CVE-2026-100532 openclaw WhatsApp before 2026.8.1 Authentication Bypass

High 7.2 Published Updated

A non-owner sender can bypass owner-only restrictions to force a WhatsApp account logout, causing service disruption and requiring manual relinking.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-100532?

CVE-2026-100532 is a high-severity missing authorization vulnerability in openclaw whatsapp, published on 26 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

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

Weakness: CWE-862

Which versions are affected by CVE-2026-100532?

How do I fix CVE-2026-100532?

No fix has been published for CVE-2026-100532 yet. Limit exposure of the affected software until one is available.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2026-100532 being exploited?

There is no known exploitation of CVE-2026-100532 in the wild and no public exploit code.

Sources

Also known as GHSA-9m4p-cqp4-jppq, GHSA-wh2c-24c2-x93p.

Is CVE-2026-100532 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free