CVE-2026-26324: SSRF in OpenClaw Node.js Package

The SSRF vulnerability in OpenClaw allows an attacker to send requests to unintended internal or external resources. By bypassing the SSRF guard, attackers can potentially access sensitive data, metadata endpoints, or internal services that should be protected. Specifically, the use of IPv4-mapped IPv6 literals (e.g., 0:0:0:0:0:ffff:7f00:1 representing 127.0.0.1) circumvents the intended filtering logic. This could lead to unauthorized access to loopback addresses, private networks, or link-local metadata, potentially exposing sensitive information or enabling further exploitation within the internal network. While no immediate exploitation is reported, the ease of bypassing the SSRF protection makes this a significant risk.

1. Reserved2026-02-13
2. Published2026-02-17
3. Modified2026-02-20
4. EPSS updated2026-03-23

The primary mitigation for CVE-2026-26324 is to upgrade to OpenClaw version 2026.2.14 or later, which includes the fix for the SSRF protection bypass. If upgrading is not immediately feasible, consider implementing a Web Application Firewall (WAF) or reverse proxy with strict filtering rules to block requests containing IPv4-mapped IPv6 literals. Additionally, review and strengthen your internal network segmentation to limit the potential blast radius of a successful SSRF attack. Monitor your application logs for unusual outbound requests, particularly those originating from within your internal network. After upgrading, confirm the fix by attempting to send a request using an IPv4-mapped IPv6 literal to a known internal resource; the request should be blocked.