CVE-2026-53838: OpenClaw · Node pairing reconnection could confuse approval scope state
Affects openclaw-cliSource GCVE Database
Not known to be exploited · CVSS 9.8 Critical : upgrade to 2026.5.28 as a priority.
Data as of 17 Nov 2026, 19:05 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.5.28
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation 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.5.28.
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 starting with OpenClaw CLI version 2026.5.27. Operators should upgrade to this version to remediate the vulnerability. Until patched, revoke any unexpected node pairings and re-pair only trusted nodes. Additionally, narrow channel and tool allowlists, avoid sharing a Gateway between mutually untrusted users, and disable the affected node pairing feature if it is not needed.
Description
A vulnerability in OpenClaw CLI allows node pairing reconnection to confuse the approval scope state, potentially broadening node authority beyond operator intent. This affects versions from 2026.1.29 up to but not including 2026.5.28. The issue arises when a paired or reconnecting node session mutates pairing state, impacting approval scope decisions. The vulnerability does not alter the trusted-operator model but can present increased authority if the affected feature is enabled and reachable. A fix is available starting with version 2026.5.27. Operators are advised to revoke unexpected node pairings and re-pair only trusted nodes until patched, and to harden configurations by narrowing allowlists and disabling the feature if not needed.