CVE-2026-42439: OpenClaw: Browser tabs action select and close routes bypassed SSRF policy
In OpenClaw before 2026.4.10, the `/tabs/action` endpoint's select and close branches acted on browser targets without applying the configured browser SSRF policy. That weakened tab-level navigation protections. 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 enforces an SSRF policy that decides which pages the browser may reach. The /tabs/action route has several branches. The select and close branches did not enforce that policy (CWE-862, CWE-918). A caller could therefore point them at targets the policy should have blocked.
The advisory is short and says only that tab-level navigation protections were weakened. It does not give a proof of concept, and I do not claim more than that. The CVSS 3.1 vector shows a network attack with low privileges, changed scope, high confidentiality impact and low integrity impact. The CVSS 4.0 vector shows no privileges at all. The two scores disagree on privileges, so treat the endpoint as reachable by any party that can talk to the browser control interface.
For a team running OpenClaw with browser access, the concern is an agent or caller that reaches internal pages despite a policy meant to keep them out.
Who is affected
The openclaw npm package, all versions below 2026.4.10. Deployments that use the browser tool and rely on its SSRF policy are the ones that matter. Check the 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, the latest release it names, includes the fix.
npm install -g openclaw@latestThe fix (PR #63332, commit 48c0347) enforces the browser SSRF policy in the select and close tab-action branches. The advisory lists no workaround.
How to tell if you were hit
Check browser control logs for /tabs/action calls with select or close actions that target internal, loopback or metadata addresses. Compare open tabs against your SSRF policy. The advisory gives no log signature.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
Summary
Browser tabs action select and close routes bypassed SSRF policy.
Affected Packages / Versions
- Package:
openclaw - Ecosystem: npm
- Affected versions:
< 2026.4.10 - Patched versions:
>= 2026.4.10
Impact
The browser /tabs/action select and close branches could operate on targets without enforcing configured browser SSRF policy, weakening tab-level navigation protections.
Technical Details
The fix enforces browser SSRF policy in the select and close tab-action branches.
Fix
The issue was fixed in #63332. The first stable tag containing the fix is v2026.4.10, and [email protected] includes the fix.
Fix Commit(s)
48c0347921b7e9438af0312968fc360ca88023f3- PR: #63332
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 @tdjackey for reporting this issue.
Credited to nicky-cc.
Questions
- Which OpenClaw version fixes CVE-2026-42439?
2026.4.10. Every earlier version is affected, and 2026.4.14 includes the fix as well.
- Which route is affected?
The browser
/tabs/actionendpoint, in its select and close branches.- How is this different from CVE-2026-42436?
CVE-2026-42436 covers snapshot, screenshot and tab routes that did not re-check the final page after navigation, fixed in 2026.4.14. This one covers missing policy enforcement in
/tabs/actionselect and close, fixed in 2026.4.10.- 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/63332
- https://github.com/openclaw/openclaw/commit/48c03479211799ec3c1305ad69037cea25ba0e1e
- https://nvd.nist.gov/vuln/detail/CVE-2026-42439
- https://github.com/openclaw/openclaw/commit/48c0347921b7e9438af0312968fc360ca88023f3
- https://www.vulncheck.com/advisories/openclaw-ssrf-policy-bypass-in-browser-tabs-action-routes
- https://github.com/advisories/GHSA-rj2p-j66c-mgqh
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
