GHSA-pfv7-rr5m-qmv6
OpenClaw has auth inconsistency on local Browser Extension Relay /extension endpoint
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.
Attack profile
How easy it is to exploit
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
What each source reports
GitHub Advisories Score used
OpenClaw has auth inconsistency on local Browser Extension Relay /extension endpoint
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.
- Record
GHSA-pfv7-rr5m-qmv6- CVSS 4.0
- 5.1 Medium
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N - Weakness
- CWE-306
- Updated
- 2026-11-02
OSV
OpenClaw has auth inconsistency on local Browser Extension Relay /extension endpoint
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.
- Record
GHSA-pfv7-rr5m-qmv6- CVSS 4.0
- 5.1 Medium
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N - Weakness
- CWE-306
- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
openclawnpm | before 2026.2.19 | 2026.2.19 |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
GHSA-pfv7-rr5m-qmv6 is a medium vulnerability (CVSS 5.1) in openclaw, published March 3, 2026. No source lists public exploit code. Fixed in openclaw 2026.2.19.