# CVE-2026-100532: openclaw WhatsApp before 2026.8.1 Authentication Bypass

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

- **Severity:** High 7.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-9m4p-cqp4-jppq, GHSA-wh2c-24c2-x93p

## 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 (Missing Authorization)

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

## Is CVE-2026-100532 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-100532 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-100532 in the wild and no public exploit code.

Affected product: openclaw whatsapp. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-100532/ (Markdown: https://insights.sbomify.com/CVE-2026-100532/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-100532
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-100532
- OSV: https://osv.dev/vulnerability/CVE-2026-100532

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-100532/
Summaries are generated and may contain mistakes; the official description above is the record.