The npm package openclaw/whatsapp before 2026.8.1 allows a non‑owner user to bypass the intended owner‑only boundary by leveraging the generic channel‑tool path. A malicious actor can request a forced login that returns a new QR code for the configured account, thereby disconnecting the gateway’s WhatsApp connection and causing a loss of availability. Because the attacker must still scan the QR code with another phone to relink the account, this vulnerability primarily enables denial‑of‑service rather than a full account takeover.

The openclaw/whatsapp npm package, specifically any installation before version 2026.8.1, is affected. The flaw does not involve WhatsApp transport authentication itself but affects the local ownership boundary that protects the login tool.

The CVSS score is 7.2, reflecting high severity. EPSS data is not available and the flaw is not listed in CISA KEV. Attackers would need access to the channel‑tool interface, which may be exposed internally or on a public endpoint depending on deployment. Given the lack of a public exploit and the requirement to scan a QR code on a separate device, the exploitability is moderate, yet it can disrupt service by severing the gateway’s connection to the WhatsApp account.