Persistent admin tokens via spoofed locality trust
Published Jun 11, 2026 · Updated Jun 11, 2026
Authentication bypass in OpenClaw before 2026.5.22 allows remote authenticated users to mint durable admin device tokens. Control UI pairing treats spoofable locality signals as sufficient trust, allowing shared access to become a persistent administrative credential. Exploitation requires network and authentication access to the pairing path; the token remains valid after shared-token rotation until the paired device is removed.
Summary
What happened
Authentication bypass in OpenClaw before 2026.5.22 allows remote authenticated users to mint durable admin device tokens. Control UI pairing treats spoofable locality signals as sufficient trust, allowing shared access to become a persistent administrative credential. Exploitation requires network and authentication access to the pairing path; the token remains valid after shared-token rotation until the paired device is removed.
The record
- CVE
- CVE-2026-53817
- Published
- Jun 11, 2026
- Updated
- Jun 11, 2026
- Vendor
- OpenClaw Foundation
- Product
- OpenClaw
- Classifications
- CWE-290, T1098
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 11, 2026CVE publishedPublication date reported by the CVE source.
- Jun 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2026.5.22
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo