CVE-2026-45000
Server-Side Request Forgery in OpenClaw Before 2026.4.20
Publication date: 2026-05-11
Last updated on: 2026-05-11
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| openclaw | openclaw | to 2026.4.20 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-918 | The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows attackers to create stored browser profiles that bypass strict SSRF policy checks and access private-network or metadata endpoints. This could potentially expose internal services or sensitive data.
Such exposure of internal or sensitive data may lead to non-compliance with data protection regulations like GDPR or HIPAA, which require strict controls over access to personal or sensitive information.
However, the vulnerability specifically affects deployments with strict-mode SSRF policies that disable private-network CDP targets; default configurations permit such endpoints, which may reduce the risk in some environments.
Overall, organizations using vulnerable versions of OpenClaw without proper SSRF restrictions could face increased risk of data exposure, potentially impacting compliance with standards that mandate protection of sensitive data.
Can you explain this vulnerability to me?
CVE-2026-45000 is a Server-Side Request Forgery (SSRF) vulnerability in OpenClaw versions before 2026.4.20. It occurs in the browser Chrome DevTools Protocol (CDP) profile creation feature, where strict-mode SSRF policy checks are skipped. This allows attackers to create stored profiles that point to private network or metadata endpoints, bypassing security policies. These malicious profiles can then be probed during normal profile status operations, potentially exposing internal services or sensitive data.
How can this vulnerability impact me? :
This vulnerability can allow attackers to bypass SSRF protections and access internal or private network endpoints that should be restricted. By creating malicious stored profiles pointing to these sensitive endpoints, attackers may probe or interact with internal services during normal profile status checks. This could lead to exposure of sensitive information or unauthorized internal network access.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves attackers creating stored browser CDP profiles that point to private-network or metadata endpoints, bypassing strict SSRF policy checks. Detection would involve monitoring for unusual or unauthorized stored CDP profiles referencing internal or private network addresses.
Since the vulnerability is related to stored profiles and SSRF policy bypass, detection could include inspecting the stored CDP profiles for suspicious hostnames or IP addresses that point to private or metadata endpoints.
No specific detection commands or tools are provided in the available resources.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, upgrade OpenClaw to version 2026.4.20 or later, where the issue has been fixed.
The fix involves properly validating CDP endpoints against the SSRF policy during profile creation and reachability checks, preventing stored profiles from referencing unauthorized private-network or metadata endpoints.
If upgrading immediately is not possible, review and restrict stored CDP profiles to ensure they do not contain hostnames or URLs pointing to private or metadata network endpoints.