<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T02:10:54.384414+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-32007</id>
    <title>CVE-2026-32007 — OpenClaw &lt; 2026.2.23 - Sandbox Bypass in apply_patch Tool via Workspace-Only Check Bypass</title>
    <updated>2026-09-29T02:10:55.420393+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> OpenClaw</p>
<p>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.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-32007"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-h9xm-j4qg-fvpg</id>
    <title>GHSA-h9xm-j4qg-fvpg — OpenClaw: Experimental apply_patch may bypass workspace-only checks in opt-in sandbox mounts (off by default)</title>
    <updated>2026-09-29T02:10:55.420584+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: openclaw</p>
<p>### 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/...`).</p>
<p>### Impact
This does **not** affect default installs.</p>
<p>Default posture:
- `agents.defaults.sandbox.mode=off` (sandbox disabled by default)
- `tools.exec.applyPatch.enabled=false` (experimental tool disabled by default)</p>
<p>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.</p>
<p>Under that opt-in setup, `apply_patch` operations could target mounted paths outside the workspace root.</p>
<p>### Affected Packages / Versions
- Package: `openclaw` (npm)
- Affected published versions: `&lt;= 2026.2.22-2`
- Fixed in code on `main`: commit `6634030be31e1a1842967df046c2f2e47490e6bf`
- Patched release: `2026.2.23`</p>
<p>### 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`).</p>
<p>### Fix Commit(s)
- `6634030be31e1a1842967df046c2f2e47490e6bf`</p>
<p>### Release Process Note
`patched_versions` is pre-set to the rel…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-h9xm-j4qg-fvpg"/>
  </entry>
</feed>
