Openclaw cli: OpenClaw has cross-account DM pairing authorization bypass via unscoped pairing store access
Affects openclaw-cliSource GCVE Database
Not known to be exploited · CVSS 3.7 Low : upgrade to 2026.2.26 when convenient.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.2.26
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/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 16 Nov 2026.
What to do
Upgrade openclaw-cli to 2026.2.26.
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 and planned for release in OpenClaw CLI version 2026.2.26. Users should upgrade to version 2026.2.26 or later once published to remediate this vulnerability. The fix enforces strict account-scoped pairing store access to prevent cross-account authorization bypass. If you cannot patch yet, administrators should be aware of the risk in multi-account setups but no additional vendor-recommended mitigations are provided.
Description
OpenClaw CLI versions up to 2026.2.25 have an authorization bypass vulnerability in multi-account setups. The flaw allows a pairing approval from one account to authorize the same sender on another account without explicit approval. This issue affects the account-scoped access control for device message pairing stores. A fix is planned for version 2026.2.26, which enforces stricter account-scoped pairing policies to prevent cross-account authorization bleed.
References
- github.com/openclaw/openclaw/security/advisories/GHSA-vjp8-wprm-2jw9 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-32067 (opens in a new tab)
- github.com/openclaw/openclaw/commit/a0c5e28f3bf0cc0cd9311f9e9ec2ca0352550dcf (opens in a new tab)
- github.com/openclaw/openclaw/commit/bce643a0bd145d3e9cb55400af33bd1b85baeb02 (opens in a new tab)
- github.com/openclaw/openclaw (opens in a new tab)
- vulncheck.com/advisories/openclaw-cross-account-authorization-bypass-in-dm-pairing-store (opens in a new tab)