openclaw
Affected
- introduced
0, fixed2026.3.11(semver)
Fixed versions
2026.3.11
Fix
- Fixed version
2026.3.11npm install [email protected]
Advisory
Also known as: CVE-2026-32978
OpenClaw: Unrecognized script runners could bypass system.run approval integrity
Summary
In affected versions of openclaw, node-host system.run approvals did not bind a mutable file operand for some script runners, including forms such as tsx and jiti. An attacker could obtain approval for a benign script-runner command, rewrite the referenced script on disk, and have the modified code execute under the already approved run context.
Impact
Deployments that rely on node-host system.run approvals for script integrity could execute rewritten local code after operator approval. This can lead to unintended local code execution as the OpenClaw runtime user.
Affected Packages and Versions
openclaw (npm)< 2026.3.112026.3.11Technical Details
The approval planner only tracked mutable script operands for a hardcoded set of interpreters and runtime forms. Commands such as tsx ./run.ts and jiti ./run.ts fell through without a bound file snapshot, so the final pre-execution revalidation step was skipped.
Fix
OpenClaw now fails closed for approval-backed interpreter and runtime commands unless it can bind exactly one concrete local file operand, and it extends direct-file binding coverage for additional runtime forms. The fix shipped in [email protected].
Workarounds
Upgrade to 2026.3.11 or later.
High Basis: The source's own band: HIGH
0, fixed 2026.3.11 (semver)2026.3.11
2026.3.11npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0