All vulnerabilities
CVE-2026-100532GHSA-9m4p-cqp4-jppq

openclaw WhatsApp before 2026.8.1 Authentication Bypass

openclaw whatsappApplications & CMS
Open in ThreatlineRecord JSON
CVSS
7.2High
ExploitationNo known exploitationNot in CISA KEV, which does not prove it is unexploitedCISA KEV
Exploit odds (EPSS)0.27%Chance of exploitation activity in the next 30 days, higher than 18% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed in2026.8.1Fixed versionCVE List
Published26 Sep 2026Updated 8 Oct 2026CVE List

What fixes it

A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.

Description

@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.

Text from CVE List

Affected versions 2

  • whatsappaffected: all versions before 2026.8.1CVE List
  • whatsappunaffected: 2026.8.1CVE List

References 2