Open-Source Security Intelligence

Know every vulnerability
before it knows you.

DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.

Checkout DevGuardView on GitHub
Search

GHSA-mr32-vwc2-5j6h

HighCVSS 7.5 / 10
Published Feb 17, 2026·Last modified Mar 6, 2026
Affected Components(0)

No affected components available

Description

Summary

In affected versions, the Browser Relay /cdp WebSocket endpoint did not require an authentication token. As a result, a website running in the browser could potentially connect to the local relay (via loopback WebSocket) and use CDP to access cookies from other open tabs and run JavaScript in the context of other tabs.

Affected Packages / Versions

  • npm: openclaw >= 2026.1.20, < 2026.2.1
  • npm: moltbot <= 0.1.0

Details

The Chrome extension Browser Relay service exposes a local WebSocket endpoint at ws://127.0.0.1:18792/cdp (default port) for forwarding Chrome DevTools Protocol (CDP) messages.

In affected versions, the /cdp upgrade path verified the TCP peer was loopback but did not require a shared secret and did not block browser-initiated cross-origin requests.

Impact

  • 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.

Fix

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.

Fix Commit(s)

  • a1e89afcc19efd641c02b24d66d689f181ae2b5c

Releases

  • openclaw@2026.2.1 includes the fix.
  • Latest published openclaw at time of writing: 2026.2.13.

Mitigation

  • Update to openclaw@>= 2026.2.1.
  • If you cannot update immediately, disable the Browser Relay extension / relay server and avoid visiting untrusted sites.

Thanks @johnatzeropath, @LeftenantZero, and @yueyueL for reporting.

Risk Scores
Base Score
7.5

The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker does not need any special privileges or access rights. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a high impact on the confidentiality of the information.

Threat Intelligence
6.9

Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.

EPSS
0.29%

The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.

Exploit
Not available

We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.

Related Vulnerabilities

Browse More

High severity
Scan your project

Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.

Checkout DevGuard