Open-Source Security Intelligence

Know every vulnerability
before it knows you.

DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.

Checkout DevGuardView on GitHub
Search

GHSA-8cp7-rp8r-mg77

MediumCVSS 6.9 / 10
Published Mar 4, 2026·Last modified Mar 4, 2026
Affected Components(0)

No affected components available

Description

Summary

OpenClaw's SSRF hostname/IP guard did not detect ISATAP embedded IPv4 addresses (...:5efe:w.x.y.z). A crafted URL containing an ISATAP IPv6 literal could embed a private IPv4 target (for example loopback) and bypass private-address filtering in URL-fetching paths.

Severity Assessment

Rated medium: the bug weakens SSRF protections in URL fetch flows, but impact depends on reaching a URL-fetching path with attacker-controlled input and is generally constrained to internal network access attempts.

Affected Packages / Versions

  • Package: openclaw (npm)
  • Affected: >=2026.1.20 <=2026.2.17
  • Latest published at patch time: 2026.2.17
  • Patched release: 2026.2.19

Security Policy Context

Per SECURITY.md, OpenClaw's web/gateway surface is intended for local use by default, public internet exposure is out-of-scope, and prompt-injection reports are out-of-scope for bounty handling. This advisory tracks a core SSRF-guard bypass in fetch protections.

Impact

This can permit SSRF-style access attempts to internal/private network targets through URL ingestion/fetch paths that rely on shared hostname/IP blocking.

Fix

  • Added RFC 5214 ISATAP embedded-IPv4 detection to the shared SSRF classifier.
  • Centralized hostname/IP blocking through isBlockedHostnameOrIp and routed relevant validators to that shared path.
  • Added regression tests for ISATAP private vs public embedded IPv4 handling.

Fix Commit(s)

  • d51929ecb52fe65e90bf36795f4247feb29eb8aa

OpenClaw thanks @zpbrent for reporting.

Risk Scores
Base Score
6.9

The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker does not need any special privileges or access rights. No user interaction is needed for the attacker to exploit this vulnerability.

Threat Intelligence
2.7

Limited exploitation activity has been observed. Close monitoring and planned remediation are recommended.

EPSS
N/A

Probability that this vulnerability will be exploited in the wild within the next 30 days.

Exploit
Not available

We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.

Browse More

Medium severity
Scan your project

Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.

Checkout DevGuard