<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>RCE on GMO Flatt Security Research</title>
    <link>https://flatt.tech/research/tags/rce/</link>
    <description>Recent content in RCE on GMO Flatt Security Research</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 01 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://flatt.tech/research/tags/rce/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Poisoning Claude Code: One GitHub Issue to Break the Supply Chain</title>
      <link>https://flatt.tech/research/posts/poisoning-claude-code-one-github-issue-to-break-the-supply-chain/</link>
      <pubDate>Mon, 01 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://flatt.tech/research/posts/poisoning-claude-code-one-github-issue-to-break-the-supply-chain/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Hello, I&amp;rsquo;m &lt;a href=&#34;https://ryotak.net&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;RyotaK&lt;/a&gt;&#xA; ( &lt;a href=&#34;https://twitter.com/ryotkak&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;@ryotkak&lt;/a&gt;&#xA;), a security researcher at GMO Flatt Security Inc.&lt;/p&gt;&#xA;&lt;p&gt;After publishing my previous article ( &lt;a href=&#34;https://flatt.tech/research/research/posts/pwning-claude-code-in-8-different-ways&#34;&gt;Pwning Claude Code in 8 Different Ways&lt;/a&gt;&#xA;), I continued investigating Claude-related products and found several more vulnerabilities.&lt;/p&gt;&#xA;&lt;p&gt;In this article, I will explain a vulnerability in Claude Code&amp;rsquo;s GitHub Actions that could allow an attacker to compromise any repository that uses the Claude Code workflow, including Anthropic&amp;rsquo;s own repositories.&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; Variants of the misconfiguration issues described in this article were &lt;a href=&#34;https://github.com/cline/cline/security/advisories/GHSA-9ppg-jx86-fqw7&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;actively exploited&lt;/a&gt;&#xA; &lt;a href=&#34;https://www.stepsecurity.io/blog/hackerbot-claw-github-actions-exploitation#attack-5-ambient-codeplatform---ai-prompt-injection&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;in the wild&lt;/a&gt;&#xA; before this article was published.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Remote Command Execution in Google Cloud with Single Directory Deletion</title>
      <link>https://flatt.tech/research/posts/remote-command-execution-in-google-cloud-with-single-directory-deletion/</link>
      <pubDate>Mon, 23 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://flatt.tech/research/posts/remote-command-execution-in-google-cloud-with-single-directory-deletion/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Hello, I&amp;rsquo;m &lt;a href=&#34;https://ryotak.net&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;RyotaK&lt;/a&gt;&#xA; (&lt;a href=&#34;https://twitter.com/ryotkak&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;@ryotkak&lt;/a&gt;&#xA;), a security engineer at GMO Flatt Security Inc.&lt;/p&gt;&#xA;&lt;p&gt;A while ago, I participated in the &lt;a href=&#34;https://bughunters.google.com/blog/5364401980899328/hardening-google-cloud-insights-from-the-latest-cloud-vrp-bugswat&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Google Cloud VRP bugSWAT,&lt;/a&gt;&#xA; a live hacking event organized by Google.&lt;/p&gt;&#xA;&lt;p&gt;During this event, I discovered a remote command execution vulnerability in one of Google Cloud&amp;rsquo;s services. As the vulnerability has now been fixed, I would like to share the technical details in this article.&lt;/p&gt;&#xA;&lt;h2 id=&#34;tldr&#34;&gt;TL;DR&lt;/h2&gt;&#xA;&lt;p&gt;Google Cloud has a product called Looker, and this product has a feature to manage Git repositories.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Pwning Claude Code in 8 Different Ways</title>
      <link>https://flatt.tech/research/posts/pwning-claude-code-in-8-different-ways/</link>
      <pubDate>Mon, 12 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://flatt.tech/research/posts/pwning-claude-code-in-8-different-ways/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Hello, I&amp;rsquo;m &lt;a href=&#34;https://ryotak.net&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;RyotaK&lt;/a&gt;&#xA; (&lt;a href=&#34;https://twitter.com/ryotkak&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;@ryotkak&lt;/a&gt;&#xA;), a security engineer at GMO Flatt Security Inc.&lt;/p&gt;&#xA;&lt;p&gt;A few months ago, I came across an interesting behavior while using Claude Code—it executed a command without my approval.&lt;/p&gt;&#xA;&lt;p&gt;Since I wasn&amp;rsquo;t using the permission bypass mode, I decided to investigate further to understand why it was able to execute commands without explicit approval.&lt;/p&gt;&#xA;&lt;h2 id=&#34;tldr&#34;&gt;TL;DR&lt;/h2&gt;&#xA;&lt;p&gt;I discovered 8 ways to execute arbitrary commands in Claude Code without user approval.&lt;/p&gt;</description>
    </item>
    <item>
      <title>CVE-2025-59489: Arbitrary Code Execution in Unity Runtime</title>
      <link>https://flatt.tech/research/posts/arbitrary-code-execution-in-unity-runtime/</link>
      <pubDate>Fri, 03 Oct 2025 00:00:00 +0000</pubDate>
      <guid>https://flatt.tech/research/posts/arbitrary-code-execution-in-unity-runtime/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Hello, I&amp;rsquo;m &lt;a href=&#34;https://ryotak.net&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;RyotaK&lt;/a&gt;&#xA; (&lt;a href=&#34;https://twitter.com/ryotkak&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;@ryotkak&lt;/a&gt;&#xA;), a security engineer at GMO Flatt Security Inc.&lt;/p&gt;&#xA;&lt;p&gt;In May 2025, I participated in the &lt;a href=&#34;https://www.youtube.com/watch?v=jiLeF0zO8Mg&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Meta Bug Bounty Researcher Conference 2025.&lt;/a&gt;&#xA;&#xA;During this event, I discovered a vulnerability (CVE-2025-59489) in the Unity Runtime that affects games and applications built on Unity 2017.1 and later.&lt;/p&gt;&#xA;&lt;p&gt;In this article, I will explain the technical aspects of this vulnerability and its impact.&lt;/p&gt;&#xA;&lt;p&gt;This vulnerability was disclosed to Unity following responsible disclosure practices.&lt;br&gt;&#xA;Unity has since released patches for Unity 2019.1 and later, as well as a Unity Binary Patch tool to address the issue, and I strongly encourage developers to download the updated versions of Unity, recompile affected games or applications, and republish as soon as possible.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Achieving RCE in famous Japanese chat tool with an obsolete Electron feature</title>
      <link>https://flatt.tech/research/posts/escaping-electron-isolation-with-obsolete-feature/</link>
      <pubDate>Wed, 19 Feb 2025 00:00:00 +0000</pubDate>
      <guid>https://flatt.tech/research/posts/escaping-electron-isolation-with-obsolete-feature/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Hello, I&amp;rsquo;m RyotaK (&lt;a href=&#34;https://twitter.com/ryotkak&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;@ryotkak&lt;/a&gt;&#xA;), a security engineer at GMO Flatt Security Inc.&lt;/p&gt;&#xA;&lt;p&gt;A while ago, I &lt;a href=&#34;https://jvn.jp/en/jp/JVN78335885/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;reported a remote code execution vulnerability&lt;/a&gt;&#xA; that chains multiple problems in Chatwork, a popular communication tool in Japan.&lt;/p&gt;&#xA;&lt;p&gt;In the report that I sent to the bug bounty platform, I used an obsolete feature of Electron to escalate to the preload context.&lt;br&gt;&#xA;As the vulnerability was interesting, I&amp;rsquo;m writing this article to share the details of it.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
