UTC
High

OpenClaw's Browser Relay /cdp websocket is missing auth which could allow cross-tab cookie access

CVE-2026-28458 · GHSA-mr32-vwc2-5j6h · published 2026-02-17 · updated 2026-03-06

Severity
High
CVSS score
7.5
Chance of exploitation (EPSS)
0.35%
Fixed in
Not in every package
  • Exploitation No known exploitation
  • Automatable No
  • Technical impact Total
  • CISA SSVC
What it is

Potential disclosure of sensitive information (for example, session cookies from other open tabs) Potential JavaScript execution in the context of other open tabs Users must have the Browser Relay extension installed and active, and must visit an untrusted site.

What to do

Upgrade openclaw to 2026.2.1 or later. No fixed release is listed yet for moltbot. Follow the source advisory for updates, and until one ships:

From the advisory, shortened (GitHub Advisory Database, CC BY 4.0)
Update to openclaw@>= 2026.2.1. If you cannot update immediately, disable the Browser Relay extension / relay server and avoid visiting untrusted sites.

The full advisory →Licence

General guidance from ShieldPi, not a vendor fix

  • Missing or bypassable authentication. Do not expose it on a network others can reach, and put authentication you control in front of it, such as an authenticating proxy or a VPN. Binding it to localhost is not enough on its own: a web page open in your browser can still reach it, so require a token as well.

openclaw now requires a per-instance shared secret header for Browser Relay access: HTTP header: x-openclaw-relay-token It also rejects /cdp WebSocket upgrades when the Origin header is present but is not chrome-extension://..., and refuses /cdp connections unless the extension is connected. a1e89afcc19efd641c02b24d66d689f181ae2b5c

Affected
PackageRegistryAffectedFixed in
moltbotnpm<= 0.1.0No fix yet
openclawnpm>= 2026.1.20, < 2026.2.12026.2.1

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].