CVE-2026-32060

In affected versions, when apply_patch was enabled and the agent ran without filesystem sandbox containment, crafted paths could cause file writes/deletes outside the configured workspace directory.

Affected Packages / Versions

• Package: openclaw (npm)
• Affected: <= 2026.2.13
• Fixed: >= 2026.2.14

Details

The non-sandbox path resolution in apply_patch did not enforce workspace containment. Inputs like ../../... or absolute paths could escape the working directory in non-sandboxed mode.

Workarounds

• Keep tools.exec.applyPatch.enabled disabled if you do not need apply_patch.
• Keep tools.exec.applyPatch.workspaceOnly at its secure default of true.
• Restrict who can trigger tool execution (and which tools are allowlisted).

Configuration Note

tools.exec.applyPatch.workspaceOnly: false intentionally opts out of workspace containment and can re-enable outside-workspace writes/deletes.

Credits

Thanks to @p80n-sec for reporting this issue.

Practical impact depends on deployment and who can trigger tool execution. This is most relevant when tool invocation is exposed to less-trusted callers or when operators expected workspace-only containment.

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-32060 has a CVSS score of 8.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.14); upgrading removes the vulnerable code path.

Kodem intelligence

• PR: https://github.com/openclaw/openclaw/pull/16405
• Merge commit: 5544646a09c0121fca7d7093812dc2de8437c7f1

1. What is CVE-2026-32060? CVE-2026-32060 is a high-severity path traversal vulnerability in openclaw (npm), affecting versions < 2026.2.14. It is fixed in 2026.2.14. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2026-32060? CVE-2026-32060 has a CVSS score of 8.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.
3. Which versions of openclaw are affected by CVE-2026-32060? openclaw (npm) versions < 2026.2.14 is affected.
4. Is there a fix for CVE-2026-32060? Yes. CVE-2026-32060 is fixed in 2026.2.14. Upgrade to this version or later.
5. Is CVE-2026-32060 exploitable, and should I be worried? Whether CVE-2026-32060 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
6. What actually determines whether CVE-2026-32060 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.
7. How do I fix CVE-2026-32060? Upgrade openclaw to 2026.2.14 or later.

Other vulnerabilities in openclaw