Severity by source
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Prior credential compromise required (PR:L) and exploitation depends on a live session existing at rotation time (AC:H); no availability impact and no scope change.
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
7Blast Radius
ecosystem impact- 1 npm packages depend on openclaw (1 direct, 0 indirect)
Ecosystem-wide dependent count for version 2026.3.31.
DescriptionCVE.org
OpenClaw before 2026.3.31 fails to terminate active WebSocket sessions when rotating device tokens. Attackers with previously compromised credentials can maintain unauthorized access through existing WebSocket connections after token rotation.
AnalysisAI
OpenClaw's gateway device.token.rotate method rotates device credentials without disconnecting live WebSocket sessions authenticated under the old token, leaving a post-compromise revocation gap in all npm openclaw releases up to and including 2026.3.28. An attacker who has already obtained valid device credentials and established an active WebSocket connection can maintain unauthorized gateway access indefinitely after an operator rotates the token - effectively nullifying the revocation action. No public exploit exists and CISA SSVC rates exploitation as none with partial technical impact; the low CVSS 4.0 score of 2.3 and EPSS of 0.03% (7th percentile) confirm this as a low-priority, post-compromise control gap rather than an initial access vector.
Technical ContextAI
OpenClaw is an npm-distributed gateway framework (CPE: cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*) that manages device pairing and token-based WebSocket authentication. The root cause is CWE-613 (Insufficient Session Expiration): the device.token.rotate server method updated the stored credential in the data store but did not invoke any session-layer teardown for existing connections authenticated with the old token. WebSocket sessions in Node.js persist until explicitly closed or the connection drops naturally, so without an explicit disconnectClientsForDevice() call the live socket remains authenticated. The fix commit (91f7a6b) adds a queueMicrotask() call immediately after rotation that invokes context.disconnectClientsForDevice(deviceId, { role }), ensuring active sessions are severed at the next event-loop tick rather than waiting for natural connection teardown. Test coverage in devices.test.ts was simultaneously added to assert that disconnectClientsForDevice is called with the correct device and role after every rotation.
RemediationAI
Upgrade the openclaw npm package to version 2026.3.31 or later; this is the first stable release containing fix commit 91f7a6b0fd67b703897e6e307762d471ca09333d (https://github.com/openclaw/openclaw/commit/91f7a6b0fd67b703897e6e307762d471ca09333d), which adds active session disconnection after every token rotation. If an immediate upgrade is not feasible, operators can achieve equivalent revocation by restarting the gateway process after rotating a device token - this forces all existing WebSocket connections to close, eliminating any residual authenticated sessions; the trade-off is a brief service interruption and reconnection overhead for all connected devices. Refer to the full security advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-rfqg-qgf8-xr9x for maintainer guidance.
Auth bypass in OpenClaw voice-call extension before 2026.2.1. EPSS 0.68%. PoC and patch available.
Privilege escalation in OpenClaw (pre-2026.3.28) allows unauthenticated remote attackers to gain administrative access b
OpenClaw versions 2026.2.22 through 2026.2.24 contain a privilege escalation vulnerability that allows authenticated att
An authorization mismatch vulnerability in OpenClaw versions prior to 2026.3.1 allows authenticated users with operator.
OpenClaw versions prior to 2026.1.29 automatically establish WebSocket connections to attacker-controlled gateway URLs e
Path traversal in OpenClaw through version 2026.3.23 enables unauthenticated remote attackers to read arbitrary files in
OpenClaw sandbox browser functionality launches x11vnc for noVNC observer sessions without requiring authentication, all
OpenClaw versions before 2026.2.26 allow authenticated attackers to write arbitrary files outside the workspace director
OpenClaw versions prior to 2026.2.22 contain a shell environment variable injection vulnerability in the system.run func
OpenClaw versions prior to 2026.2.22 contain a resource exhaustion vulnerability where the application fails to consiste
OpenClaw versions prior to 2026.3.1 contain a sandbox escape vulnerability that allows authenticated attackers with low
OpenClaw versions 2026.1.30 and below fail to validate Telegram webhook secret tokens when `channels.telegram.webhookSec
Same weakness CWE-613 – Insufficient Session Expiration
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-25340
GHSA-wwc3-c577-533m