CVE-2026-53817: OpenClaw: Control UI locality spoofing could mint a durable admin device token

The Control UI pairing path used locality-derived signals to decide whether to trust a pairing request. Those signals could be spoofed, so trust was stronger than it should have been. The advisory does not name the signals or describe the code change.

The attacker is not anonymous. They need a foothold that reaches the pairing path: access to a LAN-bound gateway, or the shared Control UI token. The advisory states this is not an unauthenticated internet exposure issue. The CVSS 3.1 vector reflects it (adjacent network, low privileges).

What they gain is persistence. A temporary or shared access path becomes a paired device with an admin-capable token. That token can stay valid after you rotate the shared gateway token, unless you remove the paired device. For a team running OpenClaw next to AI agents, that means an admin session on the agent gateway that survives the usual cleanup step.

The npm package openclaw in all versions before 2026.5.22. The risk applies to configurations such as LAN-bound gateways or shared-token Control UI access, where locality signals counted as enough for pairing decisions.

npm ls openclaw

If you run it globally, use npm ls -g openclaw. Any result below 2026.5.22 is affected.

Upgrade to [email protected] or later, the first stable patched version:

npm install [email protected]

For deployments you cannot upgrade yet, the advisory says to remove unexpected paired devices and to avoid exposing Control UI pairing paths on networks with untrusted clients. Rotating the shared gateway token alone does not revoke a device that already paired. The advisory does not document a command for listing or removing paired devices, so check the OpenClaw documentation for your version.

Review the list of paired devices in your gateway and remove any you do not recognize, mainly ones paired from LAN addresses or around the time a shared token was in use. Compare pairing timestamps with who had Control UI access. The advisory names no log line or file to search for. If you ran an affected version on a shared network, assume a rogue device may exist and clear the list, then rotate the shared gateway token.

Summary

In affected LAN/shared-token Control UI deployments, a caller could spoof locality information used during Control UI pairing and obtain a durable admin-capable device token.

This issue is limited to deployments where the caller already has the network/authentication foothold needed to reach the Control UI pairing path. It is not an unauthenticated internet exposure issue.

Affected configurations

This affects configurations such as LAN-bound gateways or shared-token Control UI access where locality signals were accepted as sufficient for pairing decisions.

Impact

A temporary or shared Control UI access path could be turned into a persistent admin device token. That token could remain useful after the shared gateway token was rotated, unless the paired device was removed.

The issue is a pairing/locality validation problem: locality-derived trust was stronger than it should have been.

Patched Versions

The first stable patched version is 2026.5.22.

Mitigations

Upgrade to [email protected] or later. For older deployments, remove unexpected paired devices and avoid exposing Control UI pairing paths on networks with untrusted clients.