<?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>Sat, 03 Oct 2026 08:31:20 +0000</lastBuildDate>
    <item>
      <title>BREW-openclaw-cli-CVE-2026-32007 — OpenClaw: Experimental apply_patch may bypass workspace-only checks in opt-in sandbox mounts (off by default)</title>
      <link>https://cve.radiocsirt.org/vuln/brew-openclaw-cli-cve-2026-32007</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: openclaw-cli&lt;/p&gt;
&lt;p&gt;### Summary
In some opt-in sandbox configurations, the **experimental** `apply_patch` tool did not consistently apply workspace-only checks to mounted paths (for example `/agent/...`).&lt;/p&gt;
&lt;p&gt;### Impact
This does **not** affect default installs.&lt;/p&gt;
&lt;p&gt;Default posture:
- `agents.defaults.sandbox.mode=off` (sandbox disabled by default)
- `tools.exec.applyPatch.enabled=false` (experimental tool disabled by default)&lt;/p&gt;
&lt;p&gt;This behavior applies only when all of the following are enabled/configured:
- sandbox mode,
- experimental `apply_patch`,
- workspace-only expectations (`tools.fs.workspaceOnly=true` and/or `tools.exec.applyPatch.workspaceOnly=true`),
- and writable mounts outside workspace.&lt;/p&gt;
&lt;p&gt;Under that opt-in setup, `apply_patch` operations could target mounted paths outside the workspace root.&lt;/p&gt;
&lt;p&gt;### Affected Packages / Versions
- Package: `openclaw` (npm)
- Affected published versions: `&amp;lt;= 2026.2.22-2`
- Fixed in code on `main`: commit `6634030be31e1a1842967df046c2f2e47490e6bf`
- Patched release: `2026.2.23`&lt;/p&gt;
&lt;p&gt;### Technical Details
In the sandbox path flow, `apply_patch` used `sandbox.bridge.resolvePath(...)` without applying the same workspace-root assertion used by other filesystem tools. The fix makes `apply_patch` follow the same workspace-only enforcement for sandbox-resolved paths (unless explicitly disabled with `tools.exec.applyPatch.workspaceOnly=false`).&lt;/p&gt;
&lt;p&gt;### Fix Commit(s)
- `6634030be31e1a1842967df046c2f2e47490e6bf`&lt;/p&gt;
&lt;p&gt;### Release Process Note
`patched_versions` is pre-set to the rel…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: openclaw-cli&lt;/p&gt;
&lt;p&gt;### Summary
In some opt-in sandbox configurations, the **experimental** `apply_patch` tool did not consistently apply workspace-only checks to mounted paths (for example `/agent/...`).&lt;/p&gt;
&lt;p&gt;### Impact
This does **not** affect default installs.&lt;/p&gt;
&lt;p&gt;Default posture:
- `agents.defaults.sandbox.mode=off` (sandbox disabled by default)
- `tools.exec.applyPatch.enabled=false` (experimental tool disabled by default)&lt;/p&gt;
&lt;p&gt;This behavior applies only when all of the following are enabled/configured:
- sandbox mode,
- experimental `apply_patch`,
- workspace-only expectations (`tools.fs.workspaceOnly=true` and/or `tools.exec.applyPatch.workspaceOnly=true`),
- and writable mounts outside workspace.&lt;/p&gt;
&lt;p&gt;Under that opt-in setup, `apply_patch` operations could target mounted paths outside the workspace root.&lt;/p&gt;
&lt;p&gt;### Affected Packages / Versions
- Package: `openclaw` (npm)
- Affected published versions: `&amp;lt;= 2026.2.22-2`
- Fixed in code on `main`: commit `6634030be31e1a1842967df046c2f2e47490e6bf`
- Patched release: `2026.2.23`&lt;/p&gt;
&lt;p&gt;### Technical Details
In the sandbox path flow, `apply_patch` used `sandbox.bridge.resolvePath(...)` without applying the same workspace-root assertion used by other filesystem tools. The fix makes `apply_patch` follow the same workspace-only enforcement for sandbox-resolved paths (unless explicitly disabled with `tools.exec.applyPatch.workspaceOnly=false`).&lt;/p&gt;
&lt;p&gt;### Fix Commit(s)
- `6634030be31e1a1842967df046c2f2e47490e6bf`&lt;/p&gt;
&lt;p&gt;### Release Process Note
`patched_versions` is pre-set to the rel…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-openclaw-cli-cve-2026-32007</guid>
    </item>
    <item>
      <title>EUVD-2026-329404</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-329404</link>
      <description>EUVD-2026-329404</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-329404</guid>
    </item>
    <item>
      <title>fkie_cve-2026-32007</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-32007</link>
      <description>&lt;p&gt;OpenClaw versions prior to 2026.2.23 contain a path traversal vulnerability in the experimental apply_patch tool that allows attackers with sandbox access to modify files outside the workspace directory by exploiting inconsistent enforcement of workspace-only checks on mounted paths. Attackers can use apply_patch operations on writable mounts outside the workspace root to access and modify arbitrary files on the system.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;OpenClaw versions prior to 2026.2.23 contain a path traversal vulnerability in the experimental apply_patch tool that allows attackers with sandbox access to modify files outside the workspace directory by exploiting inconsistent enforcement of workspace-only checks on mounted paths. Attackers can use apply_patch operations on writable mounts outside the workspace root to access and modify arbitrary files on the system.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-32007</guid>
    </item>
    <item>
      <title>GHSA-h9xm-j4qg-fvpg — OpenClaw: Experimental apply_patch may bypass workspace-only checks in opt-in sandbox mounts (off by default)</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-h9xm-j4qg-fvpg</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: openclaw&lt;/p&gt;
&lt;p&gt;### Summary
In some opt-in sandbox configurations, the **experimental** `apply_patch` tool did not consistently apply workspace-only checks to mounted paths (for example `/agent/...`).&lt;/p&gt;
&lt;p&gt;### Impact
This does **not** affect default installs.&lt;/p&gt;
&lt;p&gt;Default posture:
- `agents.defaults.sandbox.mode=off` (sandbox disabled by default)
- `tools.exec.applyPatch.enabled=false` (experimental tool disabled by default)&lt;/p&gt;
&lt;p&gt;This behavior applies only when all of the following are enabled/configured:
- sandbox mode,
- experimental `apply_patch`,
- workspace-only expectations (`tools.fs.workspaceOnly=true` and/or `tools.exec.applyPatch.workspaceOnly=true`),
- and writable mounts outside workspace.&lt;/p&gt;
&lt;p&gt;Under that opt-in setup, `apply_patch` operations could target mounted paths outside the workspace root.&lt;/p&gt;
&lt;p&gt;### Affected Packages / Versions
- Package: `openclaw` (npm)
- Affected published versions: `&amp;lt;= 2026.2.22-2`
- Fixed in code on `main`: commit `6634030be31e1a1842967df046c2f2e47490e6bf`
- Patched release: `2026.2.23`&lt;/p&gt;
&lt;p&gt;### Technical Details
In the sandbox path flow, `apply_patch` used `sandbox.bridge.resolvePath(...)` without applying the same workspace-root assertion used by other filesystem tools. The fix makes `apply_patch` follow the same workspace-only enforcement for sandbox-resolved paths (unless explicitly disabled with `tools.exec.applyPatch.workspaceOnly=false`).&lt;/p&gt;
&lt;p&gt;### Fix Commit(s)
- `6634030be31e1a1842967df046c2f2e47490e6bf`&lt;/p&gt;
&lt;p&gt;### Release Process Note
`patched_versions` is pre-set to the rel…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: openclaw&lt;/p&gt;
&lt;p&gt;### Summary
In some opt-in sandbox configurations, the **experimental** `apply_patch` tool did not consistently apply workspace-only checks to mounted paths (for example `/agent/...`).&lt;/p&gt;
&lt;p&gt;### Impact
This does **not** affect default installs.&lt;/p&gt;
&lt;p&gt;Default posture:
- `agents.defaults.sandbox.mode=off` (sandbox disabled by default)
- `tools.exec.applyPatch.enabled=false` (experimental tool disabled by default)&lt;/p&gt;
&lt;p&gt;This behavior applies only when all of the following are enabled/configured:
- sandbox mode,
- experimental `apply_patch`,
- workspace-only expectations (`tools.fs.workspaceOnly=true` and/or `tools.exec.applyPatch.workspaceOnly=true`),
- and writable mounts outside workspace.&lt;/p&gt;
&lt;p&gt;Under that opt-in setup, `apply_patch` operations could target mounted paths outside the workspace root.&lt;/p&gt;
&lt;p&gt;### Affected Packages / Versions
- Package: `openclaw` (npm)
- Affected published versions: `&amp;lt;= 2026.2.22-2`
- Fixed in code on `main`: commit `6634030be31e1a1842967df046c2f2e47490e6bf`
- Patched release: `2026.2.23`&lt;/p&gt;
&lt;p&gt;### Technical Details
In the sandbox path flow, `apply_patch` used `sandbox.bridge.resolvePath(...)` without applying the same workspace-root assertion used by other filesystem tools. The fix makes `apply_patch` follow the same workspace-only enforcement for sandbox-resolved paths (unless explicitly disabled with `tools.exec.applyPatch.workspaceOnly=false`).&lt;/p&gt;
&lt;p&gt;### Fix Commit(s)
- `6634030be31e1a1842967df046c2f2e47490e6bf`&lt;/p&gt;
&lt;p&gt;### Release Process Note
`patched_versions` is pre-set to the rel…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-h9xm-j4qg-fvpg</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-0490 — OpenClaw: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0490</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in OpenClaw ausnutzen, um beliebigen Programmcode auszuführen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, vertrauliche Informationen offenzulegen, Cross-Site-Scripting-Angriffe durchzuführen, einen Denial-of-Service-Zustand zu verursachen oder andere nicht näher bezeichnete Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in OpenClaw ausnutzen, um beliebigen Programmcode auszuführen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, vertrauliche Informationen offenzulegen, Cross-Site-Scripting-Angriffe durchzuführen, einen Denial-of-Service-Zustand zu verursachen oder andere nicht näher bezeichnete Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0490</guid>
    </item>
  </channel>
</rss>
