CVE-2026-32019
SSRF Bypass via Incomplete IPv4 Validation in OpenClaw
Publication date: 2026-03-19
Last updated on: 2026-04-20
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| openclaw | openclaw | to 2026.2.22 (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
Can you explain this vulnerability to me?
This vulnerability exists in OpenClaw versions prior to 2026.2.22 due to incomplete validation of IPv4 special-use ranges in the isPrivateIpv4() function.
Because of this incomplete validation, requests to RFC-reserved IPv4 ranges can bypass Server-Side Request Forgery (SSRF) policy checks.
Attackers who have network access to these special-use IPv4 ranges can exploit the web_fetch functionality to access addresses that should be blocked, such as the 198.18.0.0/15 range and other non-global IP ranges.
How can this vulnerability impact me? :
This vulnerability can allow an attacker with network reachability to special-use IPv4 ranges to bypass SSRF protections and access internal or otherwise restricted network resources.
Such unauthorized access could lead to information disclosure, unauthorized interactions with internal services, or further exploitation depending on the network environment.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know