CVE-2026-32905: OpenClaw · Non-owner chat senders could issue device-pairing bootstrap codes
Affects openclaw-cliSource GCVE Database
Not known to be exploited · CVSS 8.3 High : upgrade to 2026.5.4 soon.
Data as of 18 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.5.4
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:LExploitation 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 18 Nov 2026.
What to do
Upgrade openclaw-cli to 2026.5.4.
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
Upgrade OpenClaw CLI to version 2026.5.4 or later. Review all paired devices and remove any unexpected or unauthorized entries. Limit chat command access in shared channels to only those users who should manage device pairing to reduce risk.
Description
OpenClaw CLI versions from 2026.1.29 up to but not including 2026.5.4 contain a vulnerability where authorized non-owner chat senders can issue device-pairing bootstrap codes via the /pair command. This allows them to enroll devices with operator/node capabilities, which retain persistent credentials until removed. The vulnerability requires the attacker to already have permission to send commands through a configured chat channel and does not affect unauthenticated users. The issue is fixed in version 2026.5.4.