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.
Published: 2026-09-26
Score: 7.2 High
EPSS: n/a
KEV: No
Impact: Authentication Bypass
Action: Apply patch
AI Analysis

Impact

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.

Affected Systems

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.

Risk and Exploitability

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.

Generated by OpenCVE AI on September 26, 2026 at 03:44 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade openclaw/whatsapp to version 2026.8.1 or later
  • Restrict access to the generic channel‑tool path so that only authorized owners can invoke it
  • Verify that the owner‑only boundary is enforced in your deployment configuration

Generated by OpenCVE AI on September 26, 2026 at 03:44 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 26 Sep 2026 02:30:00 +0000

Type Values Removed Values Added
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.
Title openclaw WhatsApp before 2026.8.1 Authentication Bypass
Weaknesses CWE-862
References
Metrics cvssV3_1

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H'}

cvssV4_0

{'score': 7.2, 'vector': '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'}

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-09-26T02:18:33.146Z

Reserved: 2026-09-26T01:00:40.148Z

Link: CVE-2026-100532

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-26T03:16:58.660

Modified: 2026-09-26T03:16:58.660

Link: CVE-2026-100532

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-26T03:45:04Z

Weaknesses