CVE-2026-32026

Sandbox media local-path validation accepted absolute paths under host tmp, even when those paths were outside the active sandbox root.

Affected Packages / Versions

• Package: openclaw (npm)
• Latest published version verified during triage: 2026.2.23
• Affected versions: <= 2026.2.23
• Patched versions (planned next release): >= 2026.2.24

Details

In affected versions, sandbox media path resolution allowed absolute host tmp paths as trusted media inputs when they were under os.tmpdir(), without requiring that the path stay within the active sandboxRoot.
Because outbound attachment hydration consumed these paths as already validated, this enabled out-of-sandbox host tmp file reads and exfiltration through attachment delivery.

Fix Commit(s)

• d3da67c7a9b463edc1a9b1c1f7af107a34ca32f5
• 79a7b3d22ef92e36a4031093d80a0acb0d82f351
• def993dbd843ff28f2b3bad5cc24603874ba9f1e

Release Process Note

The advisory is pre-set with patched version 2026.2.24 so it is ready for publication once that npm release is available.

OpenClaw thanks @tdjackey for reporting.

Publication Update (2026-02-25)

[email protected] is published on npm and contains the fix commit(s) listed above. This advisory now marks >= 2026.2.24 as patched.

• Confidentiality impact: high for deployments relying on sandboxRoot as a strict local filesystem boundary.
• Practical impact: attacker-controlled media references could read and attach host tmp files outside the sandbox workspace boundary.

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-32026 has a CVSS score of 6.5 (Medium). 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.24); upgrading removes the vulnerable code path.

Kodem intelligence

• Restrict sandbox tmp-path acceptance to OpenClaw-managed temp roots only.
• Default SDK/extension temp helpers to OpenClaw-managed temp roots.
• Add CI guardrails to prevent broad tmp-root regressions in messaging/channel code paths.

1. What is CVE-2026-32026? CVE-2026-32026 is a medium-severity path traversal vulnerability in openclaw (npm), affecting versions <= 2026.2.23. It is fixed in 2026.2.24. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2026-32026? CVE-2026-32026 has a CVSS score of 6.5 (Medium). 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-32026? openclaw (npm) versions <= 2026.2.23 is affected.
4. Is there a fix for CVE-2026-32026? Yes. CVE-2026-32026 is fixed in 2026.2.24. Upgrade to this version or later.
5. Is CVE-2026-32026 exploitable, and should I be worried? Whether CVE-2026-32026 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-32026 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-32026? Upgrade openclaw to 2026.2.24 or later.