CVE-2026-53843: OpenClaw: Pairing-scoped device session could restore revoked node token authority

When an operator revokes a device's node token, the device should lose node authority until someone approves it again through the normal pairing flow. In affected releases, a surviving same-device session with pairing-related scope could re-establish that authority on its own. The revoked device then gets back its node WebSocket access.

The attacker must already be a paired device with a session in place, which matches the low-privilege network vector. The advisory says this does not allow unauthenticated device creation, and the impact is limited to devices with a legitimate pairing or session foothold.

The damage is to revocation as an operator control. A compromised or retired node that the operator thinks is cut off can keep node-level access, with high confidentiality, integrity and availability impact in the CVSS 3.1 vector. VulnCheck classes it as insufficient session expiration (CWE-613). Teams that revoke node tokens to respond to a lost laptop, a leaked token or an offboarded device are the ones who rely on revocation working.

The npm package openclaw before 2026.5.26, in deployments where an already paired device keeps a same-device session with pairing-related scope after its node token is revoked. Check the Gateway version:

npm ls -g openclaw

Upgrade to openclaw 2026.5.26 or later, the first stable patched version.

npm install -g [email protected]

If you revoked a node token on an older version, restart the Gateway and remove and re-pair the affected device. That makes sure no stale session stays active.

List the devices paired with your Gateway and compare them with the node tokens you revoked. A revoked device that still has an active node WebSocket connection, or that reconnects after revocation without a new pairing approval, is the sign. Check Gateway logs for node connections from device ids whose tokens were revoked earlier. After upgrading and re-pairing, confirm the old session no longer connects.

Summary

In affected releases, a surviving pairing-scoped session for a device could re-establish node token authority after that node token had been revoked. Revocation should require the device to lose that authority unless it is approved again through the normal pairing flow.

This issue affects token revocation and device-role containment. It does not allow unauthenticated device creation.

Affected configurations

This affects deployments where an already paired device keeps a same-device session with pairing-related scope after its node token is revoked.

Impact

A device that should have lost node WebSocket authority could regain it without renewed approval. That weakens revocation as an operator control and can keep node-level access alive longer than intended.

The impact is limited to devices that already had a legitimate pairing/session foothold.

Patched Versions

The first stable patched version is 2026.5.26.

Mitigations

Upgrade to [email protected] or later. If a node token was revoked on an older version, restart the gateway and remove/re-pair the affected device to ensure no stale session remains active.