Approval bypass via pairing-state mutation
Published Jun 12, 2026 · Updated Jun 12, 2026
Authorization bypass in OpenClaw before 2026.5.27 allows remote authenticated users to gain broader node authority during reconnection. The node-pairing reconnection path mutates pairing state between the approval-scope check and its use, allowing stale or broader authority to govern the session. The feature must be enabled and reachable by a paired or reconnecting node; the consequence is limited to approval boundaries crossed by that node.
Summary
What happened
Authorization bypass in OpenClaw before 2026.5.27 allows remote authenticated users to gain broader node authority during reconnection. The node-pairing reconnection path mutates pairing state between the approval-scope check and its use, allowing stale or broader authority to govern the session. The feature must be enabled and reachable by a paired or reconnecting node; the consequence is limited to approval boundaries crossed by that node.
The record
- CVE
- CVE-2026-53838
- Published
- Jun 12, 2026
- Updated
- Jun 12, 2026
- Vendor
- OpenClaw Foundation
- Product
- OpenClaw
- Classifications
- CWE-367, CAPEC-29, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 12, 2026CVE publishedPublication date reported by the CVE source.
- Jun 12, 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.27
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.
Weakness, pattern, technique
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