CVE-2026-100532: 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 Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
@openclaw/whatsappto a version that resolves this vulnerability.Fixed in 2026.8.1
Event History
Frequently Asked Questions
Who can exploit this issue?
An admitted non-owner sender who can steer the generic channel-tool path to invoke the WhatsApp login tool can exploit it. The issue does not allow an unauthenticated outsider to bypass WhatsApp transport authentication.
What is the practical impact of a successful exploit?
The attacker can force a WhatsApp login request and receive a new QR code for a configured account, which disconnects the Gateway's WhatsApp account and causes loss of availability. Relinking the account fully requires the attacker to scan that QR code using another phone.
Are default owner-only restrictions sufficient protection?
No. The affected generic channel-tool path fails to preserve the originating sender's owner status, so the owner-only boundary is not enforced for the WhatsApp login tool.
What versions should be remediated?
Upgrade @openclaw/whatsapp to version 2026.8.1 or later. Versions before 2026.8.1 are affected.