Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain adjacent network access
-
DeliveryScan Docker bridge subnet for CDP port 9222
-
ExploitConnect to exposed Chrome DevTools Protocol endpoint
-
ExecutionIssue CDP commands to control browser
-
PersistExfiltrate credentials from browser storage
-
ImpactManipulate agent-viewed content
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V13 - Configuration Secure default settings
|
| Exploitation Conditions | Exploitation requires the OpenClaw sandbox browser feature to be actively running with default (vulnerable) configuration in versions before 2026.4.10. The attacker must have adjacent network access to the Docker bridge network where the sandbox browser container is deployed - typically achieved by controlling a peer container in the same Docker Compose stack, Kubernetes pod network, or local area network with bridge access. The CDP relay must be started (default behavior when sandbox browser is initialized). Exploitation is NOT possible from the public internet (AV:A limits to adjacent networks), does NOT require authentication to OpenClaw itself (PR:N), and does NOT require user interaction (UI:N). Docker network isolation (user-defined bridge with --internal flag or network policies blocking inter-container traffic) and non-default cdpSourceRange configuration limit exposure. |
| Impact | CVSS 9.0 (AV:A/AC:L/PR:N/UI:N) indicates adjacent network exploitation with low complexity and no authentication, resulting in high impact to confidentiality, integrity, availability, and subsequent system scope. The Adjacent Vector (AV:A) limits exploitation to attackers on the same network segment as the Docker bridge - typically peer containers in the same pod/stack or local network attackers with Docker network access. Attack Complexity Low (AC:L) and Present Attack Requirements (AT:P) reflect that exploitation requires the sandbox browser to be running with default (pre-patch) configuration. No EPSS score or CISA KEV status provided, suggesting limited real-world exploitation visibility at time of analysis. The vulnerability's real-world severity depends heavily on deployment architecture: multi-tenant container environments where untrusted workloads share Docker networks face critical risk, while single-tenant or network-isolated deployments have reduced exposure. The comprehensive fix with fail-closed defaults and unit test coverage indicates vendor confidence in remediation completeness. Primary risk is to AI agent platforms, browser automation frameworks, and testing infrastructure using OpenClaw in shared Docker environments. |
| Exploit ScenarioDerived | An attacker deploys a malicious container on the same Docker bridge network as an OpenClaw sandbox browser instance. The attacker scans the bridge subnet (e.g., 172.21.0.0/16) and discovers the CDP relay listening on port 9222 with 0.0.0.0 binding. Using a standard CDP client library, the attacker connects to the exposed endpoint and issues Chrome DevTools Protocol commands to navigate sandboxed browser sessions, inject JavaScript into agent-controlled pages, exfiltrate cookies/tokens from browser storage, or manipulate DOM content to poison agent training data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – May 06, 2026
Chrome DevTools Protocol exposure in OpenClaw sandbox browser allows adjacent network attackers to remotely control sandboxed Chrome instances and access sensitive data. The CDP relay binds to 0.0.0.0 without source IP restrictions in versions before 2026.4.10, enabling attackers on the same Docker network to bypass sandbox isolation and execute arbitrary JavaScript in browser contexts. Vendor-released patch available (v2026.4.10); no public exploit identified at time of analysis. CVSS 9.0 reflects adjacent network attack vector with high confidentiality, integrity, and availability impact across virtual and system scopes.
RemediationAI
Upgrade to OpenClaw 2026.4.10 or later (npm install openclaw@2026.4.14 contains the fix). The patch enforces CDP source range validation by auto-deriving restrictions from the Docker bridge gateway IP (e.g., 172.21.0.1/32) or requiring explicit OPENCLAW_BROWSER_CDP_SOURCE_RANGE configuration. Fix commit fbf11ebdb7110632f93926d0ac7b48f04cb44d77 and PR #61404 available at https://github.com/openclaw/openclaw/commit/fbf11ebdb7110632f93926d0ac7b48f04cb44d77. For deployments unable to upgrade immediately, set OPENCLAW_BROWSER_CDP_SOURCE_RANGE environment variable to a restrictive CIDR (e.g., 127.0.0.1/32 for localhost-only, or the specific management host IP) before starting the sandbox browser container. Note this workaround requires modifying container orchestration configs and will prevent the socat relay from starting if left unset in patched versions. Network-level mitigation: isolate OpenClaw sandbox containers using Docker network segmentation or firewall rules blocking CDP port (default 9222) from untrusted peers; this adds operational complexity and does not address the root cause. No workaround fully replicates the patch's fail-closed design.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in npm
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Chrome DevTools Protocol (CDP) is a remote debugging interface that provides full control over Chrome/Chromium browser instances, including JavaScript execution, DOM manipulation, network interception, and access to cookies/storage. OpenClaw's sandbox browser architecture uses a socat relay to forward CDP connections from the host to the containerized Chrome instance. The vulnerability stems from CWE-1188 (Insecure Default Initialization of Resource) - the relay bound to 0.0.0.0 on all interfaces without IP source filtering. The fix introduces mandatory CDP_SOURCE_RANGE validation: the entrypoint script now refuses to start socat unless an explicit CIDR is provided, auto-deriving it from the Docker bridge network gateway (e.g., 172.21.0.1/32) or using 127.0.0.1/32 for network=none deployments. For non-bridge network drivers (macvlan, ipvlan), the fix requires explicit administrator configuration to prevent accidental exposure. The patch adds comprehensive test coverage for gateway derivation, IPv6 rejection (relay binds IPv4 only), and network driver edge cases.
Know when Openclaw gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
2DescriptionCVE.org
OpenClaw before 2026.4.10 contains an improper network binding vulnerability in the sandbox browser CDP relay that exposes Chrome DevTools Protocol on 0.0.0.0. Attackers can access the DevTools protocol outside intended local sandbox boundaries by exploiting the overly broad binding configuration.
Executive ViewAI
OpenClaw sandbox browser versions before 2026.4.10 expose Chrome DevTools Protocol without network segmentation, allowing attackers on the same Docker network to remotely control browser instances and exfiltrate sensitive data. Organizations using OpenClaw in containerized environments face immediate risk of sandbox escape and credential theft if deployed without network isolation controls.
Vendor-released patch: v2026.4.10. Interim mitigations (if patch deployment delayed): Restrict CDP relay to localhost only via configuration (if supported); place OpenClaw containers in isolated Docker networks with explicit deny-all ingress rules; implement host-level firewall rules blocking inbound access to CDP ports from untrusted networks; disable CDP relay if functionality not required.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Auth bypass in OpenClaw voice-call extension before 2026.2.1. EPSS 0.68%. PoC and patch available.
Privilege escalation in OpenClaw (pre-2026.3.28) allows unauthenticated remote attackers to gain administrative access b
OpenClaw versions 2026.2.22 through 2026.2.24 contain a privilege escalation vulnerability that allows authenticated att
An authorization mismatch vulnerability in OpenClaw versions prior to 2026.3.1 allows authenticated users with operator.
OpenClaw versions prior to 2026.1.29 automatically establish WebSocket connections to attacker-controlled gateway URLs e
Path traversal in OpenClaw through version 2026.3.23 enables unauthenticated remote attackers to read arbitrary files in
Authentication bypass in OpenClaw before 2026.5.3 allows remote attackers with low privileges to receive agent responses
Directory-context bypass in OpenClaw before 2026.8.1 allows authenticated attackers with user interaction to reuse an 'a
Unauthenticated access to the noVNC observer interface in OpenClaw's Docker sandbox browser allows anyone who can reach
OpenClaw versions before 2026.2.26 allow authenticated attackers to write arbitrary files outside the workspace director
OpenClaw versions prior to 2026.2.22 contain a shell environment variable injection vulnerability in the system.run func
OpenClaw versions prior to 2026.2.22 contain a resource exhaustion vulnerability where the application fails to consiste
EUVD-2026-28175
NVD
CVE.org
EPSS
Vulnrichment
GitHub
Exploit-DB