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)… (CVE-2026-100567)
OpenClaw Gateway versions from 2026.4.5 up to but not including 2026.8.1 contain a vulnerability where DNS pinning during hostname validation for remote Chrome DevTools Protocol (CDP) endpoints is bypassed. This allows an attacker controlling a CDP hostname or its DNS responses to exploit DNS rebinding and cause the Gateway to connect to unauthorized internal or restricted network addresses. The vulnerability is fixed in version 2026.8.1. Mitigation includes disabling hostname-based remote CDP endpoints or restricting them to trusted infrastructure.
AI Analysis
Technical Summary
The OpenClaw agent gateway (npm package 'openclaw') versions >= 2026.4.5 and < 2026.8.1 validate a single DNS resolution result for a configured remote Chrome DevTools Protocol (CDP) hostname, enforcing DNS pinning at validation time. However, the raw WebSocket and Playwright transports perform a subsequent independent DNS resolution, ignoring the initial DNS pinning. This check-then-use flaw enables an attacker who controls the approved CDP hostname or its DNS answers to exploit DNS rebinding attacks, causing the Gateway to connect to loopback, private, link-local, cloud metadata, or other addresses that would normally be blocked by SSRF policies. The impact varies depending on the remote CDP configuration, DNS timing, and accessible services from the Gateway host. The issue is resolved in version 2026.8.1.
Potential Impact
An attacker controlling an approved CDP hostname or its DNS responses can bypass DNS pinning protections and cause the Gateway to connect to internal or restricted network addresses. This can lead to server-side request forgery (SSRF) attacks with potential high confidentiality and integrity impacts, and low availability impact. The severity is high (CVSS 8.2). The actual impact depends on the Gateway's remote CDP configuration and network environment.
Mitigation Recommendations
A fix is available in OpenClaw version 2026.8.1. Users should upgrade to this version to resolve the vulnerability. As an additional mitigation, disable hostname-based remote CDP endpoints or restrict them to trusted, stable infrastructure to reduce exposure until the upgrade is applied.
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)… (CVE-2026-100567)
Description
OpenClaw Gateway versions from 2026.4.5 up to but not including 2026.8.1 contain a vulnerability where DNS pinning during hostname validation for remote Chrome DevTools Protocol (CDP) endpoints is bypassed. This allows an attacker controlling a CDP hostname or its DNS responses to exploit DNS rebinding and cause the Gateway to connect to unauthorized internal or restricted network addresses. The vulnerability is fixed in version 2026.8.1. Mitigation includes disabling hostname-based remote CDP endpoints or restricting them to trusted infrastructure.
CVSS v3.1
Score 8.2high
Affected software
pkg:github/openclaw/openclawRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The OpenClaw agent gateway (npm package 'openclaw') versions >= 2026.4.5 and < 2026.8.1 validate a single DNS resolution result for a configured remote Chrome DevTools Protocol (CDP) hostname, enforcing DNS pinning at validation time. However, the raw WebSocket and Playwright transports perform a subsequent independent DNS resolution, ignoring the initial DNS pinning. This check-then-use flaw enables an attacker who controls the approved CDP hostname or its DNS answers to exploit DNS rebinding attacks, causing the Gateway to connect to loopback, private, link-local, cloud metadata, or other addresses that would normally be blocked by SSRF policies. The impact varies depending on the remote CDP configuration, DNS timing, and accessible services from the Gateway host. The issue is resolved in version 2026.8.1.
Potential Impact
An attacker controlling an approved CDP hostname or its DNS responses can bypass DNS pinning protections and cause the Gateway to connect to internal or restricted network addresses. This can lead to server-side request forgery (SSRF) attacks with potential high confidentiality and integrity impacts, and low availability impact. The severity is high (CVSS 8.2). The actual impact depends on the Gateway's remote CDP configuration and network environment.
Mitigation Recommendations
A fix is available in OpenClaw version 2026.8.1. Users should upgrade to this version to resolve the vulnerability. As an additional mitigation, disable hostname-based remote CDP endpoints or restrict them to trusted, stable infrastructure to reduce exposure until the upgrade is applied.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-px74-p6x8-q327
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-100567"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6ab74f28f7a7c54106e13823
Added to database: 09/26/2026, 04:50:48 UTC
Last enriched: 09/26/2026, 04:54:12 UTC
Last updated: 09/27/2026, 01:47:40 UTC
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.