Cyber Resilience

CVE-2026-32019

SSRF in Openclaw ≤ 2026.2.22

Public PoCSSRF
Published
19 March 2026
Modified
20 April 2026
Patch / advisory
CVSS Score v4 2.3
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0021 11th percentile
Risk Priority 26 floored blend · peak EPSS

Summary

CVE-2026-32019 is a low-severity SSRF (CWE-918) vulnerability in Openclaw Openclaw. Its CVSS base score is 2.3 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 11th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to AC-4 (Information Flow Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-32019 is a server-side request forgery (SSRF) vulnerability, classified as CWE-918, affecting OpenClaw versions prior to 2026.2.22. The issue stems from incomplete IPv4 special-use range validation in the isPrivateIpv4() function, which fails to properly block requests to RFC-reserved ranges. This flaw enables SSRF policy bypasses within the web_fetch functionality, allowing access to non-global addresses such as 198.18.0.0/15. The vulnerability carries a CVSS v3.1 base score of 7.4 (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L) and was published on 2026-03-19.

Attackers with low privileges and network reachability to special-use IPv4 ranges can exploit this vulnerability over the network with low complexity and no user interaction required. By targeting the web_fetch functionality with crafted requests to reserved ranges, they can bypass SSRF protections, achieving low-impact confidentiality, integrity, and availability effects across a changed scope.

Mitigation requires upgrading to OpenClaw 2026.2.22 or later. Patches addressing the incomplete validation are available in the following GitHub commits: 333fbb86347998526dd514290adfd5f727caa6d9, 44dfbd23df453e51b71ef79a148c28c53e89168c, 71bd15bb4294d3d1b54386064d69cd0f5f731bd8, and f14ebd743cfc73f667fae80af70043d0ab1f88bd. Further details are provided in the GitHub Security Advisory at GHSA-4rqq-w8v4-7p47.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

OpenClaw versions prior to 2026.2.22 contain incomplete IPv4 special-use range validation in the isPrivateIpv4() function, allowing requests to RFC-reserved ranges to bypass SSRF policy checks. Attackers with network reachability to special-use IPv4 ranges can exploit web_fetch functionality to access blocked…

more

addresses such as 198.18.0.0/15 and other non-global ranges.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-22181Same product: Openclaw Openclaw
CVE-2026-44116Same product: Openclaw Openclaw
CVE-2026-28467Same product: Openclaw Openclaw
CVE-2026-32037Same product: Openclaw Openclaw
CVE-2026-53827Same product: Openclaw Openclaw
CVE-2026-41914Same product: Openclaw Openclaw
CVE-2026-41302Same product: Openclaw Openclaw
CVE-2026-44117Same product: Openclaw Openclaw
CVE-2026-62216Same product: Openclaw Openclaw
CVE-2026-43526Same product: Openclaw Openclaw

Affected Assets

openclaw
openclaw
≤ 2026.2.22

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.3.6
  • V1.5.3
  • V5.3.2
  • V10.4.7

Mitigating Controls (NIST 800-53 r5) AI

Information flow enforcement can restrict which destinations the server is allowed to contact on behalf of users.

Input validation directly stops untrusted URLs from being accepted and fetched without destination checks.

Boundary protection limits the network reach of server-initiated requests even if SSRF occurs.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure development practices directly include input validation and destination allow-listing that prevent SSRF.

DE.CM-09 partial match
prevents

Runtime monitoring of web applications and services can detect anomalous outbound requests indicative of SSRF.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover and record SSRF flaws in web applications.

PR.IR-01 partial match
prevents

Network segmentation and egress controls can limit the damage from successful SSRF requests.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Operational threat data describing SSRF campaigns can be used to tighten outbound-request allow-lists and detection rules before attackers exploit them.

References