GHSA-5v6x-rfc3-7qfr
OpenClaw has Windows system.run approval mismatch on cmd.exe /c trailing arguments
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
openclawnpmDescription
Summary
A Windows system.run approval-integrity mismatch in the cmd.exe /c path could allow trailing arguments to execute while approval/audit text reflected only a benign command string.
This requires an authenticated operator context using the approvals flow and a trusted Windows node.
Affected Packages / Versions
- Package:
openclaw(npm) - Latest published vulnerable version (as of 2026-02-21):
2026.2.19-2 - Vulnerable range:
<=2026.2.19-2 - Patched version (planned next release):
2026.2.21
Attack Scenario
- An authenticated operator approval is created for a benign command text (for example,
echo). - A
system.runrequest usescmd.exe /cwith extra trailing arguments. - Prior behavior could bind approval/audit text to the benign command while still executing the full argument tail on the node.
Impact
- Local command execution on the trusted Windows node process account.
- Approval/audit command text integrity mismatch.
Fix
- Canonicalize the full command tail after
cmd.exe /c. - Reuse one shared command canonicalization/validation path for validation, approval matching, and execution/audit text.
- Add regression coverage for trailing-argument smuggling and approval binding.
Fix Commit(s)
6007941f04df1edcca679dd6c95949744fdbd4df
Release Process Note
patched_versions is pre-set to the planned next release (2026.2.21). Once that npm release is live, this advisory can be published directly.
OpenClaw thanks @tdjackey for reporting.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | openclaw | all versions | 2026.2.21 |
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.2.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5v6x-rfc3-7qfr 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-5v6x-rfc3-7qfr 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-5v6x-rfc3-7qfr. 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-5v6x-rfc3-7qfr in your dependencies?
O3 detects GHSA-5v6x-rfc3-7qfr across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.