WhatsApp login tool could reach non-owner turns
GHSA-9m4p-cqp4-jppq · published 2026-09-11
- Severity
- High
- CVSS score
- 8.1
- Chance of exploitation (EPSS)
- No CVE
- Fixed in
- 2026.8.1
A non-owner sender able to steer the tool could disconnect or replace the Gateway's WhatsApp account, causing loss of availability and unauthorized account relinking. Successful takeover required scanning the returned QR code with another phone. The issue affected the owner-only tool boundary rather than WhatsApp transport authentication.
Upgrade @openclaw/whatsapp to 2026.8.1 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
The first stable patched version is 2026.8.1.
Upgrade @openclaw/whatsapp to 2026.8.1 or later. Until upgraded, disable the WhatsApp login tool after setup, restrict agent access to owner-controlled conversations, and avoid exposing tool-capable agents to non-owner senders.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| @openclaw/whatsapp | npm | < 2026.8.1 | 2026.8.1 |
- CriticalMarimo: Pre-Auth Remote Code Execution via Terminal WebSocket Authentication BypassmarimoExploited
- CriticalLangflow CORS misconfiguration enables Account Takeover and RCElangflowExploited
- HighLiteLLM: MCP Authentication Bypass via OAuth2 Passthrough FallbacklitellmExploited
- HighLangflow: IDOR Vulnerability in `/api/v1/responses` Endpoint Allows Authenticated Attackers to Access Another User's FlowlangflowExploited
- CriticalTodoist MCP Server: Browser DNS rebinding lets websites write and delete Todoist data through local MCP server@doist/todoist-mcp
- CriticalLangflow: Unauthenticated Flow Execution via Webhook Authentication Bypasslangflow
The impact, patch and workaround text comes from the advisory, shortened (published by OpenClaw). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.