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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 2026.8.1
Fixed in 2026.8.1
Mitigation
Upgrade whatsapp to 2026.8.1 or later.
References
- Vendor advisory github.com/openclaw/openclaw/security/advisori…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.