Affected versions
- Affected versions
- < 2026.5.22
- Fixed version
- 2026.5.22
Exploitation
Description
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.
Links
- https://github.com/advisories/GHSA-chr9-m4q2-76hw
- https://github.com/openclaw/openclaw
- https://github.com/openclaw/openclaw/security/advisories/GHSA-chr9-m4q2-76hw
- https://nvd.nist.gov/vuln/detail/CVE-2026-53817
- https://www.vulncheck.com/advisories/openclaw-control-ui-locality-spoofing-in-device-pairing
Credits
- cantinagen

