CVE-2026-42439
Server-Side Request Forgery Bypass in OpenClaw
Publication date: 2026-05-05
Last updated on: 2026-05-05
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| openclaw | openclaw | to 2026.4.10 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
What immediate steps should I take to mitigate this vulnerability?
To mitigate the CVE-2026-42439 vulnerability, you should upgrade OpenClaw to version 2026.4.10 or later, as these versions contain the patch that fixes the SSRF policy bypass in the browser tabs action routes.
This upgrade will enforce the intended SSRF policy protections and prevent unauthorized tab navigation operations via the /tabs/action endpoint.
Can you explain this vulnerability to me?
CVE-2026-42439 is a server-side request forgery (SSRF) policy bypass vulnerability found in OpenClaw versions before 2026.4.10. It affects the browser tabs action select and close routes, specifically the /tabs/action endpoint. Attackers can exploit this vulnerability to bypass the configured SSRF policy protections, allowing them to perform unauthorized tab navigation operations that should normally be restricted.
This vulnerability is caused by insufficient validation or missing authorization checks on the affected routes, categorized under CWE-862 and CWE-918, which relate to missing authorization and improper validation leading to SSRF risks.
How can this vulnerability impact me? :
This vulnerability can allow attackers with some level of access (low privileges) to bypass SSRF protections and perform unauthorized navigation operations within browser tabs. This could lead to unauthorized access to internal resources or sensitive information that the SSRF policy was designed to protect.
The impact includes potential exposure of internal services, weakening of security boundaries, and possible information disclosure. Although the CVSS v3.1 score rates it as high severity (8.5), the CVSS v4.0 score is moderate (4.9), reflecting the complexity and conditions required for exploitation.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify how the CVE-2026-42439 vulnerability affects compliance with common standards and regulations such as GDPR or HIPAA.