Openclaw cli: OpenClaw has auth inconsistency on local Browser Extension Relay /extension endpoint

OpenClaw CLI versions up to and including 2026.2.17 have a local authentication inconsistency when the optional Chrome extension relay is enabled. Specifically, the /extension WebSocket endpoint accepts unauthenticated upgrades on the loopback interface (127.0.0.1), whereas the /json/* and /cdp endpoints require authentication tokens. This inconsistency allows a local process to connect to /extension without a token and potentially interfere with extension-relay functionality. The issue is local-only with no remote network attack vector. The fix requires enforcing gateway-token authentication on both /extension and /cdp WebSocket endpoints, retaining loopback/origin checks as defense-in-depth, and unifying token configuration paths. The fix is committed in commit 7e54b6c96feb1a5c30884f2b32037b8dadd0e532.

A local attacker or process on the same machine can connect to the /extension WebSocket endpoint without authentication and interfere with the extension relay behavior. There is no remote network exploit path, so the impact is limited to local privilege contexts. This could affect the integrity or reliability of the extension relay feature for local users or processes.

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.