isPrivateIpv4() in bundled SSRF guard code missed several IPv4 special-use/non-global ranges, so web_fetch could allow targets that should be blocked by SSRF policy.
openclaw (npm)2026.2.21-2 (published 2026-02-21)<= 2026.2.21-2>= 2026.2.22Low severity. Exploitation requires network reachability to the relevant special-use ranges and a request path that reaches web_fetch URL fetching.
Affected releases used narrow IPv4 private-range checks that omitted multiple RFC special-use/non-global ranges. This allowed requests such as http://198.18.0.1/... through SSRF validation in affected releases. Follow-up hardening consolidates local-host/tailnet range checks so gateway/browser/tailnet paths share one canonical IP classification flow.
71bd15bb4294d3d1b54386064d69cd0f5f731bd844dfbd23df453e51b71ef79a148c28c53e89168c333fbb86347998526dd514290adfd5f727caa6d9f14ebd743cfc73f667fae80af70043d0ab1f88bdOpenClaw thanks @princeeismond-dot for reporting.
{
"github_reviewed": true,
"github_reviewed_at": "2026-03-04T19:03:45Z",
"cwe_ids": [
"CWE-918"
],
"severity": "MODERATE",
"nvd_published_at": "2026-03-19T22:16:35Z"
}