Openclaw cli: OpenClaw has auth inconsistency on local Browser Extension Relay /extension endpoint
Affects openclaw-cliSource GCVE Database
CVSS 5.1 Medium : upgrade to 2026.7.1 when convenient.
Data as of 19 Nov 2026, 19:34 UTC
- Patch
- Available – fixed in 2026.7.1
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NWhat to do
Upgrade openclaw-cli to 2026.7.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available that enforces gateway-token authentication on both /extension and /cdp WebSocket relay endpoints. Users should upgrade to a version later than 2026.2.17 that includes this fix. The fix also maintains loopback/origin checks as defense-in-depth but does not rely on them for authentication. No additional mitigation is required beyond applying the official fix.
Description
OpenClaw CLI has an authentication inconsistency in its local Chrome extension relay feature. The /extension WebSocket endpoint accepts unauthenticated connections on the local loopback interface, while other relay endpoints require authentication. This allows a local process on the same machine to connect without a token and interfere with extension-relay behavior. No remote exploitation is possible. A fix is available that enforces token authentication on all relay endpoints.