CVE-2026-53852: OpenClaw · Empty-scope device re-pairing could confuse caller scope containment
Affects openclaw-cliSource GCVE Database
Not known to be exploited · CVSS 5.4 Medium : upgrade to 2026.4.25 when convenient.
Data as of 17 Nov 2026, 19:05 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.4.25
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade openclaw-cli to 2026.4.25.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available in openclaw-cli version 2026.4.25. Operators should upgrade to this version to remediate the vulnerability. Until patched, it is recommended to revoke unexpected device sessions and require fresh pairing for suspicious devices. Additional mitigations include keeping channel and tool allowlists narrow, avoiding sharing a Gateway between mutually untrusted users, and disabling the affected feature when it is not needed.
Description
OpenClaw CLI versions from 2026.1.29 up to but not including 2026.4.25 contain a vulnerability where an empty-scope device re-pairing request can bypass intended scope containment controls. This may allow broader access scopes than intended during device re-pairing. The vulnerability affects configurations where the feature is enabled and reachable, with impact depending on operator setup and input trust levels. A patch is available in version 2026.4.25. Mitigations include revoking unexpected device sessions, requiring fresh pairing for suspicious devices, narrowing allowlists, avoiding shared Gateways between untrusted users, and disabling the affected feature if not needed.