GHSA-939r-rj45-g2rj is a high-severity (CVSS 8.8) CWE-829 vulnerability in openclaw. O3 Security confirms whether GHSA-939r-rj45-g2rj is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
OpenClaw: Workspace provider auth choices could auto-enable untrusted provider plugins
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.
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
Summary
Workspace provider auth choices could auto-enable untrusted provider plugins.
Affected Packages / Versions
- Package:
openclaw - Ecosystem: npm
- Affected versions:
< 2026.4.9 - Patched versions:
>= 2026.4.9
Impact
Non-interactive onboarding could select a provider auth choice shadowed by an untrusted workspace plugin, auto-enabling that plugin during auth setup.
Technical Details
The fix prefers trusted provider origins for auth choices and excludes untrusted workspace choices unless they are explicitly enabled.
Fix
The issue was fixed in #62368. The first stable tag containing the fix is v2026.4.9, and [email protected] includes the fix.
Fix Commit(s)
2d97eae53e212ae26f3aebcd6a50ffc6877f770d- PR: #62368
Release Process Note
Users should upgrade to openclaw 2026.4.9 or newer. The latest npm release, 2026.4.14, already includes the fix.
Credits
Thanks to @zpbrent for reporting this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | openclaw | all versions | 2026.4.9 |
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.4.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-939r-rj45-g2rj 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-939r-rj45-g2rj 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-939r-rj45-g2rj. 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-939r-rj45-g2rj in your dependencies?
O3 detects GHSA-939r-rj45-g2rj across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.