CVE-2026-31991: Openclaw cli · OpenClaw has Signal group allowlist authorization bypass via DM pairing-store leakage
Affects openclaw-cliSource GCVE Database
Not known to be exploited · CVSS 3.7 Low : upgrade to 2026.2.26 when convenient.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% 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 17 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 in OpenClaw CLI version 2026.2.26 that fixes the authorization bypass by isolating DM pairing-store entries and enforcing explicit group allowlist boundaries. Users should upgrade to version 2026.2.26 or later to remediate this vulnerability. No additional mitigation actions are required beyond applying the official fix.
Description
OpenClaw CLI versions up to 2026.2.25 contain an authorization bypass vulnerability in Signal group allowlist enforcement. When groupPolicy is set to allowlist, sender identities approved via direct message (DM) pairing-store could improperly bypass group allowlist checks. This occurs because DM pairing approvals leak into group allowlist evaluation, weakening the authorization boundary between DM pairing and group membership controls. The issue is fixed in version 2026.2.26 by isolating DM pairing-store entries to DM-only and enforcing explicit group allowlist boundaries.
References
- github.com/openclaw/openclaw/security/advisories/GHSA-wm8r-w8pf-2v6w (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-31991 (opens in a new tab)
- github.com/openclaw/openclaw/commit/64de4b6d6ae81e269ceb4ca16f53cda99ced967a (opens in a new tab)
- github.com/openclaw/openclaw/commit/8bdda7a651c21e98faccdbbd73081e79cffe8be0 (opens in a new tab)
- github.com/openclaw/openclaw (opens in a new tab)
- vulncheck.com/advisories/openclaw-authorization-bypass-via-dm-pairing-store-leakage-in-signal-group-allowlist (opens in a new tab)