GHSA-vfw7-6rhc-6xxg
HIGHGHSA-vfw7-6rhc-6xxg is a high-severity (CVSS 7.8) CWE-15 vulnerability in openclaw. O3 Security confirms whether GHSA-vfw7-6rhc-6xxg is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
OpenClaw Has Incomplete Fix for CVE-2026-4039: CLI Backend Environment Variable Injection via Workspace Config
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
openclawnpmDescription
Summary
Incomplete Fix for CVE-2026-4039: CLI Backend Environment Variable Injection via Workspace Config
Current Maintainer Triage
- Status: open
- Normalized severity: high
- Assessment: Real shipped malicious-workspace-config env injection in the CLI backend runner, fixed by sanitizing backend env before spawn and shipped in v2026.3.24, so advisory stays open until published.
Affected Packages / Versions
- Package:
openclaw(npm) - Latest published npm version:
2026.3.31 - Vulnerable version range:
<=2026.3.23-2 - Patched versions:
>= 2026.3.24 - First stable tag containing the fix:
v2026.3.24
Fix Commit(s)
c2fb7f1948c3226732a630256b5179a60664ec24— 2026-03-24T12:58:10-07:00
Release Process Note
- The fix is already present in released version
2026.3.24. - This draft looks ready for final maintainer disposition or publication, not additional code-fix work.
Thanks @YLChen-007 for reporting.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | openclaw | all versions | 2026.3.24 |
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.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vfw7-6rhc-6xxg 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-vfw7-6rhc-6xxg 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-vfw7-6rhc-6xxg. 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-vfw7-6rhc-6xxg in your dependencies?
O3 detects GHSA-vfw7-6rhc-6xxg across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.