GHSA-527m-976r-jf79
HIGHGHSA-527m-976r-jf79 is a high-severity (CVSS 7.7) CWE-862 vulnerability in openclaw. O3 Security confirms whether GHSA-527m-976r-jf79 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
OpenClaw: Existing-session browser interaction routes bypassed SSRF policy enforcement
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
openclawnpmDescription
Summary
Existing-session browser interaction routes bypassed SSRF policy enforcement.
Affected Packages / Versions
- Package:
openclaw - Ecosystem: npm
- Affected versions:
< 2026.4.10 - Patched versions:
>= 2026.4.10
Impact
Existing-session browser interaction routes could continue interacting with or navigating targets without applying the same SSRF navigation guard used by guarded browser routes.
Technical Details
The fix guards existing-session navigation and interaction routes with browser navigation policy checks.
Fix
The issue was fixed in #64370. The first stable tag containing the fix is v2026.4.10, and [email protected] includes the fix.
Fix Commit(s)
daeb74920d5ad986cb600625180037e23221e93a- PR: #64370
Release Process Note
Users should upgrade to openclaw 2026.4.10 or newer. The latest npm release, 2026.4.14, already includes the fix.
Credits
Thanks to @zsxsoft, with sponsorship from @KeenSecurityLab and @qclawer for reporting this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | openclaw | all versions | 2026.4.10 |
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.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-527m-976r-jf79 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-527m-976r-jf79 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-527m-976r-jf79. 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-527m-976r-jf79 in your dependencies?
O3 detects GHSA-527m-976r-jf79 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.