Know every vulnerabilitybefore 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.
GHSA-pfv7-rr5m-qmv6
No affected components available
Summary
When the optional Chrome extension relay is enabled, /extension accepted unauthenticated WebSocket upgrades while /json/* and /cdp required auth.
Affected Packages / Versions
- Package:
openclaw(npm) - Affected:
<= 2026.2.17 - Latest published npm version at triage time:
2026.2.17
Impact
This is a local-only issue on loopback (127.0.0.1) and only applies when the extension relay feature is in use. A local process on the same machine could connect to /extension without the token and interfere with extension-relay behavior.
No remote network exploit path is involved.
Fix
- Require gateway-token auth on both
/extensionand/cdprelay WebSocket endpoints. - Keep loopback/origin checks as defense-in-depth, not as authentication.
- Use one token path in setup:
gateway.auth.token/OPENCLAW_GATEWAY_TOKEN.
Fix Commit(s)
7e54b6c96feb1a5c30884f2b32037b8dadd0e532
OpenClaw thanks @tdjackey for reporting.
The vulnerability requires local access to the device to be exploited. 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.
Limited exploitation activity has been observed. Close monitoring and planned remediation are recommended.
Probability that this vulnerability will be exploited in the wild within the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard