OpenClaw's SSRF IP classifier did not treat IPv6 multicast literals (ff00::/8) as blocked/private-internal. This allowed literal multicast hosts to pass SSRF preflight checks.
A bypass in address classification existed for IPv6 multicast literals. OpenClaw's network fetch/navigation paths are constrained to HTTP/HTTPS and this was triaged as low-severity defense-in-depth hardening.
openclaw (npm)<= 2026.2.24>= 2026.2.25 The IPv6 private/internal range set omitted multicast, so addresses like ff02::1 and ff05::1:3 were not classified as blocked by the shared SSRF classifier.
baf656bc6fd7f83b6033e6dbc2548ec75028641fpatched_versions is pre-set to the planned next npm release (2026.2.25). Once that release is published on npm, the advisory is published.
OpenClaw thanks @zpbrent for reporting.
{
"github_reviewed": true,
"severity": "MODERATE",
"cwe_ids": [
"CWE-918"
],
"nvd_published_at": null,
"github_reviewed_at": "2026-03-03T21:48:55Z"
}