CVE-2026-53817: OpenClaw < 2026.5.22 - Control UI Locality Spoofing in Device Pairing
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 openclaw@2026.5.22 or later. For older deployments, remove unexpected paired devices and avoid exposing Control UI pairing paths on networks with untrusted clients.
Other sources
OpenClaw before 2026.5.22 contains a locality validation vulnerability in Control UI pairing that allows attackers with network access to spoof locality information and obtain durable admin-capable device tokens. Attackers can exploit insufficient locality-derived trust validation to convert temporary shared access into persistent administrative credentials that survive token rotation.
— NVD
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/openclawto a version that resolves this vulnerability.Fixed in 2026.5.22 - Upgrade
Upgrade
openclawto a version that resolves this vulnerability.Fixed in 2026.5.22 - Compensating control
For older deployments, remove unexpected paired devices and avoid exposing Control UI pairing paths on networks with untrusted clients.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-53817?
CVE-2026-53817 has a high severity score of 8.8.
How can I fix CVE-2026-53817?
To fix CVE-2026-53817, upgrade OpenClaw to version 2026.5.22 or later.
What type of vulnerability is CVE-2026-53817?
CVE-2026-53817 is a locality validation vulnerability in Control UI pairing.
What is the risk associated with CVE-2026-53817?
The risk level for CVE-2026-53817 is rated at 79, which indicates a significant vulnerability.
Who is affected by CVE-2026-53817?
Any users of OpenClaw versions prior to 2026.5.22 are affected by CVE-2026-53817.