openclaw
Affected
- introduced
0, fixed2026.2.2(semver)
Fixed versions
2026.2.2
Fix
- Fixed version
2026.2.2npm install [email protected]
Advisory
Also known as: CVE-2026-28472
OpenClaw's gateway connect could skip device identity checks when auth.token was present but not yet validated
Summary
The gateway WebSocket connect handshake could allow skipping device identity checks when auth.token was present but not yet validated.
Details
In src/gateway/server/ws-connection/message-handler.ts, the device-identity requirement could be bypassed based on the *presence* of a non-empty connectParams.auth.token rather than a *validated* shared-secret authentication result.
Impact
In deployments where the gateway WebSocket is reachable and connections can be authorized via Tailscale without validating the shared secret, a client could connect without providing device identity/pairing. Depending on version and configuration, this could result in operator access.
Deployment Guidance
Per OpenClaw security guidance, the gateway should only be reachable from a trusted network and by trusted users (for example, restrict Tailnet users/ACLs when using Tailscale Serve).
If the gateway WebSocket is only reachable by trusted users, there is typically no untrusted party with network access to exploit this issue.
Affected Packages / Versions
openclaw (npm)<= 2026.2.1>= 2026.2.2Fix
Device-identity skipping now requires *validated* shared-secret authentication (token/password). Tailscale-authenticated connections without validated shared secret require device identity.
Fix Commit(s)
Thanks @simecek for reporting.
Critical Basis: The source's own band: CRITICAL
0, fixed 2026.2.2 (semver)2026.2.2
2026.2.2npm 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