openclaw WhatsApp before 2026.8.1 Authentication Bypass
@openclaw/whatsapp (npm) before 2026.8.1 exposes the WhatsApp login tool through the generic channel-tool path without preserving the originating sender's owner status, so the owner-only tool boundary is not enforced. An admitted non-owner sender able to steer the tool can request a forced login and receive a new QR code for a configured account, disconnecting the Gateway's WhatsApp account and causing loss of availability; full account relinking additionally requires the attacker to scan the returned QR code with another phone. The issue affects the owner-only tool boundary rather than WhatsApp transport authentication. Fixed in 2026.8.1.
CVE-2026-100532
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: cve:CVE-2026-100532
Source reference: /containers/cna/affected/0/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Structured affected-version data
Original package identities and version rules from this source.
[
{
"vendor": "openclaw",
"product": "whatsapp",
"versions": [
{
"status": "affected",
"version": "0",
"lessThan": "2026.8.1",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "2026.8.1",
"versionType": "semver"
}
],
"packageURL": "pkg:npm/%40openclaw/whatsapp",
"defaultStatus": "unaffected"
}
]- Related CVEs
- CVE-2026-100532
Source reference:
/cveMetadata/cveId
Publisher severity
high
Source reference: /containers/cna/metrics
- Event
- #12659 · Revision 1
- Added to Heist Feed
- Publisher date