CVE-2026-43573: OpenClaw: Existing-session browser interaction routes bypassed SSRF policy enforcement
OpenClaw before 2026.4.10 did not apply the browser SSRF navigation guard to its existing-session browser interaction routes. Those routes could keep navigating and interacting with targets that the guarded routes would block. Upgrade the `openclaw` npm package to 2026.4.10 or later.
Published Apr 17, 2026 · Updated May 8, 2026 · Analysis Oct 29, 2026
What an attacker can do
OpenClaw's browser tool checks navigation against an SSRF policy. That check sat on the guarded browser routes. The routes that work on an existing browser session, for navigation and interaction, did not run the same check (CWE-862, CWE-918). A caller could use an already-open session to reach a target the policy forbids and act on it.
The attacker needs low privileges: the ability to call browser tool routes, directly or through an agent steered by crafted content. The result is access to internal pages the SSRF policy is there to protect, such as admin consoles or metadata endpoints. The CVSS 3.1 vector shows changed scope with high confidentiality impact and no integrity impact. The advisory gives no proof of concept.
This is one of several OpenClaw browser SSRF gaps fixed in the same period. It differs from the others in the route: it concerns session reuse, not tab select and close or snapshots.
Who is affected
The openclaw npm package, all versions below 2026.4.10, when the browser tool is used with existing sessions. Check the installed version:
npm ls -g openclawopenclaw
- Ecosystem
- npm
- Affected
- < 2026.4.10
- Fixed in
- 2026.4.10
- Check
npm ls openclaw
How to fix it
Upgrade to 2026.4.10 or newer. The advisory says 2026.4.14 includes the fix.
npm install -g openclaw@latestThe fix (PR #64370, commit daeb749) guards existing-session navigation and interaction routes with the browser navigation policy checks. The advisory lists no workaround.
How to tell if you were hit
Review browser tool logs for navigation or interaction in existing sessions that ends on a private, loopback or metadata address. Compare the pages open in the browser with what your SSRF policy allows. The advisory gives no log signature.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
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.
Credited to zsxsoft, KeenSecurityLab, qclawer.
Questions
- Which OpenClaw version fixes CVE-2026-43573?
2026.4.10. All earlier versions are affected, and 2026.4.14 includes the fix.
- Which routes were unguarded?
The existing-session browser navigation and interaction routes.
- How does it relate to CVE-2026-42439?
Both are browser SSRF policy bypasses fixed in 2026.4.10. CVE-2026-42439 is in the
/tabs/actionselect and close branches. This one is in the existing-session routes.- Is it exploited in the wild?
No source I read says so, and the entry has no CISA KEV data.
References
Read for this analysis:
- https://github.com/openclaw/openclaw/pull/64370
- https://github.com/openclaw/openclaw/commit/daeb74920d5ad986cb600625180037e23221e93a
- https://nvd.nist.gov/vuln/detail/CVE-2026-43573
- https://www.vulncheck.com/advisories/openclaw-ssrf-policy-bypass-in-existing-session-browser-interaction-routes
- https://github.com/advisories/GHSA-527m-976r-jf79
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
More OpenClaw vulnerabilities
All OpenClaw entriesCVE-2026-62197
OpenClaw: Browser CDP discovery could accept blocked WebSocket URLs
medium8.5Oct 21, 2026CVE-2026-35630
OpenClaw: QQBot native approval buttons did not enforce configured approver identity
high8.0Jul 2, 2026CVE-2026-53806
OpenClaw: Combined POSIX shell options could confuse exec revalidation
high8.8Jul 2, 2026CVE-2026-53809
OpenClaw: Embedded runner policy could be confused by provider aliases
medium3.8Jul 2, 2026CVE-2026-53810
OpenClaw's marketplace runtime extension metadata could point at unscanned payloads
high8.8Jul 2, 2026CVE-2026-53811
OpenClaw: Matrix allowFrom could bind to mutable display names
high8.8Jul 2, 2026
