CVE-2026-32019

HIGHPre-NVD 7.47.4—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.4 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 89% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:vulncheck, epss
7.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.4Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 addresses such as 198.18.0.0/15 and other non-global ranges.

CVSS v3
7.4
EG Score
7.4(medium)
EG Risk
33(Track)
EG Risk 33/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity74% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
11%
KEV
Not listed

Published

March 19, 2026

Last Modified

June 23, 2026

Advisory Details (6)

Auto-updated Aug 2, 2026
Patch available. Sources: github, github_commit.
generic

OpenClaw < 2026.2.22 - Incomplete IPv4 Special-Use Range Blocking in SSRF Guard | Advisories | VulnCheck

https://www.vulncheck.com/advisories/openclaw-incomplete-ipv4-special-use-range-blocking-in-ssrf-guard
github_commit

commit f14ebd743cfc (openclaw/openclaw)

Fix landed in openclaw/openclaw commit f14ebd743cfc — awaiting tagged release

https://github.com/openclaw/openclaw/commit/f14ebd743cfc73f667fae80af70043d0ab1f88bd
github_commit

commit 333fbb863479 (openclaw/openclaw)

Fix landed in openclaw/openclaw commit 333fbb863479 — awaiting tagged release

https://github.com/openclaw/openclaw/commit/333fbb86347998526dd514290adfd5f727caa6d9
github_commit

commit 44dfbd23df45 (openclaw/openclaw)

Fix landed in openclaw/openclaw commit 44dfbd23df45 — awaiting tagged release

https://github.com/openclaw/openclaw/commit/44dfbd23df453e51b71ef79a148c28c53e89168c
github_commit

commit 71bd15bb4294 (openclaw/openclaw)

Fix landed in openclaw/openclaw commit 71bd15bb4294 — awaiting tagged release

https://github.com/openclaw/openclaw/commit/71bd15bb4294d3d1b54386064d69cd0f5f731bd8
github Patch Available

Incomplete IPv4 special-use SSRF blocking in web fetch guard · Advisory · openclaw/openclaw · GitHub

https://github.com/openclaw/openclaw/security/advisories/GHSA-4rqq-w8v4-7p47

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
openclaw—2026.2.22—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 37× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 155 total refreshes for this CVE.

  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-24 14:17 UTCEPSS rescore
  3. 2026-08-23 00:19 UTCEPSS rescore
  4. 2026-08-21 23:49 UTCEPSS rescore
  5. 2026-08-19 17:03 UTCEPSS rescore
  6. 2026-08-18 13:48 UTCEPSS rescore
  7. 2026-08-17 13:47 UTCEPSS rescore
  8. 2026-08-16 14:56 UTCEPSS rescore
  9. 2026-08-16 11:07 UTCEG score recompute
  10. 2026-08-16 02:14 UTCEPSS rescore
  11. 2026-08-15 01:30 UTCEPSS rescore
  12. 2026-08-14 07:18 UTCEG score recompute
  13. 2026-08-13 22:00 UTCEPSS rescore
  14. 2026-08-12 22:01 UTCEG score recompute
  15. 2026-08-12 13:50 UTCEPSS rescore
  16. 2026-08-11 21:26 UTCEG score recompute
  17. 2026-08-11 04:30 UTCEG score recompute
  18. 2026-08-11 00:00 UTCEPSS rescore
  19. 2026-08-09 18:12 UTCEG score recompute
  20. 2026-08-09 13:46 UTCEPSS rescore
  21. 2026-08-09 06:51 UTCEG score recompute
  22. 2026-08-08 16:37 UTCEPSS rescore
  23. 2026-08-07 17:21 UTCEG score recompute
  24. 2026-08-06 19:24 UTCEG score recompute
  25. 2026-08-06 13:46 UTCEPSS rescore
Show 75 more
  1. 2026-08-06 01:31 UTCEG score recompute
  2. 2026-08-05 19:17 UTCEPSS rescore
  3. 2026-08-04 15:10 UTCEPSS rescore
  4. 2026-08-04 10:38 UTCEPSS rescore
  5. 2026-08-04 00:40 UTCEG score recompute
  6. 2026-08-03 10:36 UTCEPSS rescore
  7. 2026-08-02 16:27 UTCEG score recompute
  8. 2026-08-02 02:27 UTCEPSS rescore
  9. 2026-08-01 04:16 UTCEPSS rescore
  10. 2026-07-30 16:28 UTCEPSS rescore
  11. 2026-07-30 01:30 UTCEPSS rescore
  12. 2026-07-28 15:36 UTCEPSS rescore
  13. 2026-07-26 14:54 UTCEPSS rescore
  14. 2026-07-26 14:54 UTCEPSS rescore
  15. 2026-07-25 14:18 UTCEPSS rescore
  16. 2026-07-25 14:17 UTCEPSS rescore
  17. 2026-07-24 14:17 UTCEPSS rescore
  18. 2026-07-23 14:18 UTCEPSS rescore
  19. 2026-07-23 14:18 UTCEPSS rescore
  20. 2026-07-23 03:08 UTCEG score recompute
  21. 2026-07-22 14:08 UTCEPSS rescore
  22. 2026-07-22 14:08 UTCEPSS rescore
  23. 2026-07-21 15:24 UTCEPSS rescore
  24. 2026-07-21 15:24 UTCEPSS rescore
  25. 2026-07-20 17:08 UTCEPSS rescore
  26. 2026-07-20 17:08 UTCEPSS rescore
  27. 2026-07-19 14:31 UTCEPSS rescore
  28. 2026-07-19 14:31 UTCEPSS rescore
  29. 2026-07-19 02:29 UTCEPSS rescore
  30. 2026-07-18 10:04 UTCEPSS rescore
  31. 2026-07-18 10:04 UTCEPSS rescore
  32. 2026-07-17 07:46 UTCOSV refresh
  33. 2026-07-16 17:03 UTCEPSS rescore
  34. 2026-07-16 17:03 UTCEPSS rescore
  35. 2026-07-15 16:57 UTCEPSS rescore
  36. 2026-07-15 16:57 UTCEPSS rescore
  37. 2026-07-15 02:00 UTCEPSS rescore
  38. 2026-07-15 02:00 UTCEPSS rescore
  39. 2026-07-13 22:30 UTCEPSS rescore
  40. 2026-07-13 06:13 UTCEPSS rescore
  41. 2026-07-13 06:13 UTCEPSS rescore
  42. 2026-07-12 05:46 UTCEPSS rescore
  43. 2026-07-11 08:27 UTCEPSS rescore
  44. 2026-07-09 19:10 UTCEPSS rescore
  45. 2026-07-08 15:15 UTCEPSS rescore
  46. 2026-07-07 13:46 UTCEPSS rescore
  47. 2026-07-06 16:27 UTCEPSS rescore
  48. 2026-07-06 16:27 UTCEPSS rescore
  49. 2026-07-05 02:30 UTCEPSS rescore
  50. 2026-07-04 06:31 UTCEPSS rescore
  51. 2026-07-01 15:06 UTCEPSS rescore
  52. 2026-06-30 23:22 UTCEPSS rescore
  53. 2026-06-29 14:06 UTCEPSS rescore
  54. 2026-06-29 14:06 UTCEPSS rescore
  55. 2026-06-29 06:02 UTCOSV refresh
  56. 2026-06-28 14:07 UTCEPSS rescore
  57. 2026-06-28 14:07 UTCEPSS rescore
  58. 2026-06-28 04:56 UTCEPSS rescore
  59. 2026-06-28 04:56 UTCEPSS rescore
  60. 2026-06-27 03:08 UTCEPSS rescore
  61. 2026-06-25 13:49 UTCEPSS rescore
  62. 2026-06-25 13:49 UTCEPSS rescore
  63. 2026-06-24 14:05 UTCEPSS rescore
  64. 2026-06-23 21:33 UTCEPSS rescore
  65. 2026-06-23 21:33 UTCEPSS rescore
  66. 2026-06-22 14:25 UTCEPSS rescore
  67. 2026-06-22 14:25 UTCEPSS rescore
  68. 2026-06-21 14:56 UTCEPSS rescore
  69. 2026-06-21 14:56 UTCEPSS rescore
  70. 2026-06-21 01:59 UTCEPSS rescore
  71. 2026-06-19 19:25 UTCEPSS rescore
  72. 2026-06-19 19:25 UTCEPSS rescore
  73. 2026-06-18 17:52 UTCEPSS rescore
  74. 2026-06-18 17:52 UTCEPSS rescore
  75. 2026-06-17 17:53 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-32019?
CVE-2026-32019 is a high vulnerability published on March 19, 2026. 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…
When was CVE-2026-32019 disclosed?
CVE-2026-32019 was first published in the National Vulnerability Database on March 19, 2026, with the most recent update on June 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-32019 actively exploited?
CVE-2026-32019 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 89.4% of all scored CVEs.
What is the CVSS score of CVE-2026-32019?
CVE-2026-32019 has a CVSS v4.0 base score of 7.4 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-32019?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32019, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-32019

Explore →

Is Your Infrastructure Affected by CVE-2026-32019?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs