<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 08 Oct 2026 03:52:02 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-267596</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-267596</link>
      <description>EUVD-2026-267596</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-267596</guid>
    </item>
    <item>
      <title>fkie_cve-2026-25725</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-25725</link>
      <description>&lt;p&gt;Claude Code is an agentic coding tool. Prior to version 2.1.2, Claude Code&amp;#39;s bubblewrap sandboxing mechanism failed to properly protect the .claude/settings.json configuration file when it did not exist at startup. While the parent directory was mounted as writable and .claude/settings.local.json was explicitly protected with read-only constraints, settings.json was not protected if it was missing. This allowed malicious code running inside the sandbox to create this file and inject persistent hooks (such as SessionStart commands) that would execute with host privileges when Claude Code was restarted. This issue has been patched in version 2.1.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Claude Code is an agentic coding tool. Prior to version 2.1.2, Claude Code&amp;#39;s bubblewrap sandboxing mechanism failed to properly protect the .claude/settings.json configuration file when it did not exist at startup. While the parent directory was mounted as writable and .claude/settings.local.json was explicitly protected with read-only constraints, settings.json was not protected if it was missing. This allowed malicious code running inside the sandbox to create this file and inject persistent hooks (such as SessionStart commands) that would execute with host privileges when Claude Code was restarted. This issue has been patched in version 2.1.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-25725</guid>
    </item>
    <item>
      <title>GHSA-ff64-7w26-62rf — Claude Code has Sandbox Escape via Persistent Configuration Injection in settings.json</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-ff64-7w26-62rf</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @anthropic-ai/claude-code&lt;/p&gt;
&lt;p&gt;Claude Code&amp;#39;s bubblewrap sandboxing mechanism failed to properly protect the .claude/settings.json configuration file when it did not exist at startup. While the parent directory was mounted as writable and .claude/settings.local.json was explicitly protected with read-only constraints, settings.json was not protected if it was missing. This allowed malicious code running inside the sandbox to create this file and inject persistent hooks (such as SessionStart commands) that would execute with host privileges when Claude Code was restarted.&lt;/p&gt;
&lt;p&gt;Users on standard Claude Code auto-update received this fix automatically. Users performing manual updates are advised to update to the latest version.&lt;/p&gt;
&lt;p&gt;Claude Code thanks hackerone.com/edbr for reporting this issue!&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @anthropic-ai/claude-code&lt;/p&gt;
&lt;p&gt;Claude Code&amp;#39;s bubblewrap sandboxing mechanism failed to properly protect the .claude/settings.json configuration file when it did not exist at startup. While the parent directory was mounted as writable and .claude/settings.local.json was explicitly protected with read-only constraints, settings.json was not protected if it was missing. This allowed malicious code running inside the sandbox to create this file and inject persistent hooks (such as SessionStart commands) that would execute with host privileges when Claude Code was restarted.&lt;/p&gt;
&lt;p&gt;Users on standard Claude Code auto-update received this fix automatically. Users performing manual updates are advised to update to the latest version.&lt;/p&gt;
&lt;p&gt;Claude Code thanks hackerone.com/edbr for reporting this issue!&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-ff64-7w26-62rf</guid>
    </item>
  </channel>
</rss>
