---
id: CVE-2026-100532
title: >-
  @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
summary: >-
  @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-own…
severity: high
cvss: 8.1
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H'
cwe:
  - CWE-862
vendor: openclaw
product: whatsapp
affected:
  - whatsapp < 2026.8.1
published: '2026-09-26'
updated: '2026-09-26'
sourceUpdated: '2026-09-26T03:16:58.660'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-100532'
references:
  - url: >-
      https://github.com/openclaw/openclaw/security/advisories/GHSA-9m4p-cqp4-jppq
    label: disclosure@vulncheck.com
  - url: >-
      https://www.vulncheck.com/advisories/openclaw-whatsapp-before-2026.8.1-authentication-bypass
    label: disclosure@vulncheck.com
tags:
  - nvd
  - cve.org
ingestedAt: '2026-09-26T03:25:24.675Z'
---

## Overview

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

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.