CVE-2026-53852
Description
OpenClaw before 2026.4.25 allows authenticated operators to bypass scope containment by sending empty-scope device re-pairing requests, potentially restoring broader access.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
OpenClaw before 2026.4.25 allows authenticated operators to bypass scope containment by sending empty-scope device re-pairing requests, potentially restoring broader access.
Vulnerability
OpenClaw before version 2026.4.25 contains a scope containment bypass vulnerability in the device re-pairing feature. When a re-pairing request is submitted with an empty scope set, the intended containment guard is skipped, allowing the restoration of scopes broader than the caller should grant [1][2]. The affected feature must be enabled and reachable for exploitation to occur.
Exploitation
An attacker must be an authenticated operator with the ability to submit device re-pairing requests. No additional user interaction is required beyond the operator's action. The attacker sends a re-pairing request with an empty scope set, which bypasses the containment check and restores or retains broader scopes than intended [1][2].
Impact
Successful exploitation allows the attacker to retain or restore unauthorized device access with scopes broader than the caller's intended permissions. This can lead to low confidentiality and low integrity impacts, as reflected in the CVSS v3 score of 5.4 (Medium) [2]. The practical impact depends on the operator's configuration and whether lower-trust input can reach the vulnerable path [1].
Mitigation
The vulnerability is fixed in OpenClaw version 2026.4.25 [1]. As a workaround until patching is possible, revoke unexpected device sessions and require fresh pairing for suspicious devices. Additionally, keep channel and tool allowlists narrow, avoid sharing a single Gateway between mutually untrusted users, and disable the affected feature when it is not needed [1]. No known exploitation in the wild has been reported as of publication.
AI Insight generated on Jun 16, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
2News mentions
0No linked articles in our index yet.