CVE-2026-32007: OpenClaw: Experimental apply_patch may bypass workspace-only checks in opt-in sandbox mounts (off by default)
Summary In some opt-in sandbox configurations, the experimental applypatch tool did not consistently apply workspace-only checks to mounted paths (for example /agent/...). Impact This does not affect default installs.
Published Mar 3, 2026 · Updated Mar 30, 2026
Affected packages
openclaw
- Ecosystem
- npm
- Affected
- < 2026.2.23
- Fixed in
- 2026.2.23
- Check
npm ls openclaw
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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/...).
Impact
This does not affect default installs.
Default posture:
agents.defaults.sandbox.mode=off(sandbox disabled by default)tools.exec.applyPatch.enabled=false(experimental tool disabled by default)
This behavior applies only when all of the following are enabled/configured:
- sandbox mode,
- experimental
apply_patch, - workspace-only expectations (
tools.fs.workspaceOnly=trueand/ortools.exec.applyPatch.workspaceOnly=true), - and writable mounts outside workspace.
Under that opt-in setup, apply_patch operations could target mounted paths outside the workspace root.
Affected Packages / Versions
- Package:
openclaw(npm) - Affected published versions:
<= 2026.2.22-2 - Fixed in code on
main: commit6634030be31e1a1842967df046c2f2e47490e6bf - Patched release:
2026.2.23
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).
Fix Commit(s)
6634030be31e1a1842967df046c2f2e47490e6bf
Release Process Note
patched_versions is pre-set to the released version (2026.2.23). Patched in 2026.2.23 and published.
OpenClaw thanks @tdjackey for reporting.
Credited to tdjackey.
References
- https://github.com/openclaw/openclaw/security/advisories/GHSA-h9xm-j4qg-fvpg
- https://github.com/openclaw/openclaw/commit/6634030be31e1a1842967df046c2f2e47490e6bf
- https://nvd.nist.gov/vuln/detail/CVE-2026-32007
- https://www.vulncheck.com/advisories/openclaw-sandbox-bypass-in-apply-patch-tool-via-workspace-only-check-bypass
- https://github.com/advisories/GHSA-h9xm-j4qg-fvpg
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More OpenClaw vulnerabilities
All OpenClaw entriesCVE-2026-35630
OpenClaw: QQBot native approval buttons did not enforce configured approver identity
high8.0Jul 2, 2026CVE-2026-53806
OpenClaw: Combined POSIX shell options could confuse exec revalidation
high8.8Jul 2, 2026CVE-2026-53809
OpenClaw: Embedded runner policy could be confused by provider aliases
medium3.8Jul 2, 2026CVE-2026-53810
OpenClaw's marketplace runtime extension metadata could point at unscanned payloads
high8.8Jul 2, 2026CVE-2026-53811
OpenClaw: Matrix allowFrom could bind to mutable display names
high8.8Jul 2, 2026CVE-2026-53812
OpenClaw's browser act interactions could bypass private-network navigation checks
medium7.7Jul 2, 2026
