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/...).
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.
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.
Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.
CVE-2026-32007 has a CVSS score of 6.8 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.2.23); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-32007? CVE-2026-32007 is a high-severity path traversal vulnerability in openclaw (npm), affecting versions < 2026.2.23. It is fixed in 2026.2.23. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
- How severe is CVE-2026-32007? CVE-2026-32007 has a CVSS score of 6.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of openclaw are affected by CVE-2026-32007? openclaw (npm) versions < 2026.2.23 is affected.
- Is there a fix for CVE-2026-32007? Yes. CVE-2026-32007 is fixed in 2026.2.23. Upgrade to this version or later.
- Is CVE-2026-32007 exploitable, and should I be worried? Whether CVE-2026-32007 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-32007 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-32007? Upgrade
openclawto 2026.2.23 or later.