OpenClaw has auth inconsistency on local Browser Extension Relay /extension endpoint
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-306.
Summary
### 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 `/extension` and `/cdp` relay 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.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | openclaw (npm) | before 2026.2.19 | 2026.2.19 | Patch available | GHSA-pfv7-rr5m-qmv6 |
- openclaw (npm) Vendor— Affected before 2026.2.19 Fixed in 2026.2.19 Patch available GHSA-pfv7-rr5m-qmv6
Remediation
- Fix · GHSA-pfv7-rr5m-qmv6 openclaw (npm) Fixed in 2026.2.19 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-pfv7-rr5m-qmv6
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences