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-32979
OpenClaw: Unbound interpreter and runtime commands could bypass node-host approval integrity
Summary
In affected versions of openclaw, node-host system.run approvals could still execute rewritten local code for interpreter and runtime commands when OpenClaw could not bind exactly one concrete local file operand during approval planning.
Impact
Deployments using node-host system.run approval mode could approve a benign local script and then execute different local code if that script changed before execution. This can lead to unintended local code execution as the OpenClaw runtime user.
Affected Packages and Versions
openclaw (npm)<= 2026.3.82026.3.11Technical Details
The approval flow treated some interpreter and runtime forms as approval-backed even when it could not honestly bind a single direct local script file. That left residual approval-integrity gaps for runtime forms outside the directly bound file set.
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 best-effort direct-file binding 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