CyberRota Analysis
AI-GeneratedThe vulnerability affects the OpenClaw agent gateway in specific versions of the npm package, allowing an attacker to exploit a DNS rebinding issue that bypasses initial DNS validation. This could lead to unauthorized access to sensitive services by redirecting the Gateway to restricted addresses, depending on the remote Chrome DevTools Protocol (CDP) configuration. Organizations using affected versions should prioritize updating to version 2026.8.1 or implement mitigations by disabling or restricting hostname-based remote CDP endpoints to trusted infrastructure.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
OpenClaw is an agent gateway distributed as the npm package 'openclaw'. In versions >= 2026.4.5 and < 2026.8.1, the Gateway validated a single DNS resolution result for a configured remote Chrome DevTools Protocol (CDP) hostname, but the raw WebSocket and Playwright transports performed a later, independent DNS resolution, discarding the DNS pinning enforced at validation time. An attacker who controls an approved CDP hostname or its DNS answers can exploit this check-then-use gap via DNS rebinding to make the Gateway connect to a loopback, private, link-local, cloud metadata, or other SSRF-policy-denied address. The impact depends on the remote CDP configuration, DNS timing, and the services reachable from the Gateway host. The issue is fixed in 2026.8.1; as a mitigation, disable hostname-based remote CDP endpoints or restrict them to trusted, stable infrastructure.