Openclaw cli: OpenClaw's Browser Relay /cdp websocket is missing auth which could allow cross-tab cookie access
Affects openclaw-cliSource GCVE Database
Not known to be exploited · CVSS 7.5 High : upgrade to 2026.2.1 soon.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.2.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade openclaw-cli to 2026.2.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in openclaw version 2026.2.1 and later, which enforces authentication via a shared secret header and restricts WebSocket connections by Origin. Users should update to openclaw@>=2026.2.1 to remediate this vulnerability. If immediate updating is not possible, users should disable the Browser Relay extension or relay server and avoid visiting untrusted websites until patched.
Description
OpenClaw CLI versions from 2026.1.29 up to but not including 2026.2.1 have a vulnerability in the Browser Relay /cdp WebSocket endpoint that lacks authentication. This allows a website running in the browser to connect to the local relay via loopback WebSocket and potentially access cookies from other open tabs or execute JavaScript in their context. The issue is fixed in openclaw version 2026.2.1 by requiring a per-instance shared secret header and restricting WebSocket upgrades based on the Origin header.
References
- github.com/openclaw/openclaw/security/advisories/GHSA-mr32-vwc2-5j6h (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-28458 (opens in a new tab)
- github.com/openclaw/openclaw/commit/a1e89afcc19efd641c02b24d66d689f181ae2b5c (opens in a new tab)
- github.com/openclaw/openclaw (opens in a new tab)
- github.com/openclaw/openclaw/releases/tag/v2026.2.1 (opens in a new tab)
- vulncheck.com/advisories/openclaw-missing-authentication-in-browser-relay-cdp-websocket-endpoint (opens in a new tab)