openclaw
Affected
- introduced
0, fixed2026.2.19(semver)
Fixed versions
2026.2.19
Fix
- Fixed version
2026.2.19npm install [email protected]
Advisory
Also known as: None
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
openclaw (npm)<= 2026.2.172026.2.17Impact
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
/extension and /cdp relay WebSocket endpoints.gateway.auth.token / OPENCLAW_GATEWAY_TOKEN.Fix Commit(s)
7e54b6c96feb1a5c30884f2b32037b8dadd0e532OpenClaw thanks @tdjackey for reporting.
Medium Basis: The source's own band: MODERATE
0, fixed 2026.2.19 (semver)2026.2.19
2026.2.19npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0