GHSA-8g75-q649-6pv6 is a medium-severity (CVSS 6.3) CWE-367 vulnerability in openclaw. O3 Security confirms whether GHSA-8g75-q649-6pv6 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
OpenClaw's system.run approvals did not bind mutable script operands across approval and execution
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
openclawnpmDescription
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)
c76d29208bf6a7f058d2cf582519d28069e42240cf3a479bd1204f62eef7dd82b4aa328749ae6c91
Release Verification
- npm
2026.3.7remains vulnerable. - npm
2026.3.8contains the completed fix.
Thanks @tdjackey for reporting.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | openclaw | all versions | 2026.3.8 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update openclaw to 2026.3.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8g75-q649-6pv6 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-8g75-q649-6pv6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-8g75-q649-6pv6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-8g75-q649-6pv6 in your dependencies?
O3 detects GHSA-8g75-q649-6pv6 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.