CVE-2026-100532: openclaw whatsapp · Missing Authorization
Affects openclaw whatsappSource CVE Database V5
Not known to be exploited · CVSS 7.2 High : upgrade to 2026.8.1 soon.
Data as of 7 Nov 2026, 23:24 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.8.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 26 Sep 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 7 Nov 2026.
What to do
Upgrade whatsapp and @openclaw/whatsapp to 2026.8.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| openclawwhatsapp | Affected
| Fixed in
|
npm@openclaw/whatsapppkg:npm/@openclaw/whatsappOther 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 to version 2026.8.1 or later, where the missing authorization issue is fixed. No other mitigations are specified. Patch status is confirmed by the vendor advisory stating the fix is in 2026.8.1.
Description
A missing authorization vulnerability in @openclaw/whatsapp (npm) before version 2026.8.1 allows non-owner users to access an owner-only WhatsApp login tool. This flaw lets attackers request a forced login and obtain a new QR code for a configured account, disconnecting the Gateway's WhatsApp account and causing availability loss. Full account takeover requires scanning the QR code with another device. The issue is fixed in version 2026.8.1.