CVE-2026-32921

OpenClaw's system.run approval flow did not bind mutable interpreter-style script operands across approval and execution.

A caller could obtain approval for an execution such as sh ./script.sh, rewrite the approved script before execution, and then execute different content under the previously approved command shape. The approved argv values remained the same, but the mutable script operand content could drift after approval.

Latest published npm version verified vulnerable: 2026.3.7

The initial March 7, 2026 fix in c76d29208bf6a7f058d2cf582519d28069e42240 added approval binding for shell scripts and a narrow interpreter set, but follow-up maintainer review on March 8, 2026 found that bun and deno script operands still did not produce mutableFileOperand snapshots.

A complete fix shipped on March 9, 2026 in cf3a479bd1204f62eef7dd82b4aa328749ae6c91, which binds approved bun and deno run script operands to on-disk file snapshots and denies post-approval script drift before execution.

Affected Packages / Versions

• Package: openclaw (npm)
• Affected versions: <= 2026.3.7
• Patched version: 2026.3.8

Fix Commit(s)

• c76d29208bf6a7f058d2cf582519d28069e42240
• cf3a479bd1204f62eef7dd82b4aa328749ae6c91

Release Verification

• npm 2026.3.7 remains vulnerable.
• npm 2026.3.8 contains the completed fix.

Thanks @tdjackey for reporting.

CVE-2026-32921 has a CVSS score of 6.3 (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.3.8); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-32921? CVE-2026-32921 is a medium-severity security vulnerability in openclaw (npm), affecting versions <= 2026.3.7. It is fixed in 2026.3.8.
2. How severe is CVE-2026-32921? CVE-2026-32921 has a CVSS score of 6.3 (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-32921? openclaw (npm) versions <= 2026.3.7 is affected.
4. Is there a fix for CVE-2026-32921? Yes. CVE-2026-32921 is fixed in 2026.3.8. Upgrade to this version or later.
5. Is CVE-2026-32921 exploitable, and should I be worried? Whether CVE-2026-32921 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-32921 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-32921? Upgrade openclaw to 2026.3.8 or later.