https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 28 Sep 2026 19:38:13 +0000 https://vulnerability.circl.lu/vuln/cve-2026-32978 <p><strong>Affected:</strong> OpenClaw</p> <p>OpenClaw before 2026.3.11 contains an approval integrity vulnerability where system.run approvals fail to bind mutable file operands for certain script runners like tsx and jiti. Attackers can obtain approval for benign script commands, rewrite referenced scripts on disk, and execute modified code under the approved run context.</p> <p><strong>Affected:</strong> OpenClaw</p> <p>OpenClaw before 2026.3.11 contains an approval integrity vulnerability where system.run approvals fail to bind mutable file operands for certain script runners like tsx and jiti. Attackers can obtain approval for benign script commands, rewrite referenced scripts on disk, and execute modified code under the approved run context.</p> https://vulnerability.circl.lu/vuln/cve-2026-32978 https://vulnerability.circl.lu/vuln/ghsa-qc36-x95h-7j53 <p><strong>Affected:</strong> npm: openclaw</p> <p>## 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.</p> <p>## 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.</p> <p>## Affected Packages and Versions - Package: `openclaw` (npm) - Affected versions: `&lt; 2026.3.11` - Fixed in: `2026.3.11`</p> <p>## Technical 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.</p> <p>## 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 `openclaw@2026.3.11`.</p> <p>## Workarounds Upgrade to `2026.3.11` or later.</p> <p><strong>Affected:</strong> npm: openclaw</p> <p>## 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.</p> <p>## 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.</p> <p>## Affected Packages and Versions - Package: `openclaw` (npm) - Affected versions: `&lt; 2026.3.11` - Fixed in: `2026.3.11`</p> <p>## Technical 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.</p> <p>## 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 `openclaw@2026.3.11`.</p> <p>## Workarounds Upgrade to `2026.3.11` or later.</p> https://vulnerability.circl.lu/vuln/ghsa-qc36-x95h-7j53