Skip to content

AAK-MCP-WHATSAPP-CVE-2026-46555-001: WhatsApp MCP (verygoodplugins/whatsapp-mcp) below 0.2.1 (unauthenticated loopback bridge + media_path traversal → file exfil)

Severity
HIGH
Category
Supply Chain (supply-chain)
Scanner
agent_audit_kit/scanners/mcp_cve_pins_2026_07.py
Auto-fixable
No.
SARIF name
WhatsAppMcpUnauthBridgeTraversal

What it detects

The WhatsApp MCP Server's whatsapp-bridge HTTP API before 0.2.1 listens on 127.0.0.1:8080 with no authentication and no Host-header validation, and its /api/send endpoint accepts an absolute media_path with no directory confinement. Any local process running as the same user — which in an MCP session includes sibling MCP servers, IDE extensions, and tool-triggered flows — can send WhatsApp messages from the paired account and read then exfiltrate arbitrary user-readable files (SSH keys, browser session data, dotfiles) as document attachments; the missing Host validation also enables DNS-rebinding from a visited webpage (CVE-2026-46555, CVSS 7.7). Fixed in 0.2.1, which adds required bearer-token auth, a Host allow-list, and media_path confinement. The project is the GitHub repository verygoodplugins/whatsapp-mcp, which ships as a clone and release assets and on no registry; npm's and PyPI's whatsapp-mcp are other projects. A reference to the repository that names an earlier release is reported.

How to fix

Update the verygoodplugins/whatsapp-mcp checkout or release to v0.2.1 or later and pin that tag, then restart both the bridge and the MCP server so the server reads the bridge token. Require the bridge bearer token on all requests, enable Host-header allow-listing, and confine media_path to a configured root (reject absolute paths and ..). Do not run the bridge next to untrusted local MCP servers, browser extensions, or other untrusted processes.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-MCP-WHATSAPP-CVE-2026-46555-001

Limitations

Reads a reference to github.com/verygoodplugins/whatsapp-mcp that names a release below v0.2.1: a git URL with @v0.2.0 or @refs/tags/v0.2.0, a lockfile's git source with rev= or tag=, a /releases/download/ asset or an /archive/ tarball, and a tag, rev, ref or reference key beside a git or url key that names the repository (uv sources, Poetry, Pipfile, poetry.lock). It reads requirements*.txt, *.mcp.yaml and *.mcp.yml at any depth and, at the project root only, pyproject.toml, Pipfile, package.json, .mcp.json, mcp.json, claude_desktop_config.json and the Pipfile.lock, poetry.lock, uv.lock, package-lock.json, pnpm-lock.yaml and yarn.lock lockfiles. The install the project's README documents, a clone run with uv --directory <path> run main.py, states no version and is not reported, and neither is a reference by commit or branch, or one in .cursor/mcp.json, .vscode/mcp.json, a sub-directory manifest (services/api/pyproject.toml) or pdm.lock. npm's and PyPI's whatsapp-mcp, and PyPI's whatsapp-mcp-server, are other projects and are not read. A file over 2 MB, or a lockfile over 32 MiB, is not read.

References

  • CVE: CVE-2026-46555
  • OWASP MCP Top 10: MCP04:2025 (Software Supply Chain Attacks & Dependency Tampering), MCP07:2025 (Insufficient Authentication & Authorization)
  • OWASP Agentic Top 10: ASI02 (Tool Misuse and Exploitation), ASI04 (Agentic Supply Chain Vulnerabilities)
  • Adversa AI MCP Top 25 (AAK-defined ids): ADV-AUTH-01 (Missing Authentication)
  • CSA AI Controls Matrix (AICM): IAM-01, IVS-04, STA-08

All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-WHATSAPP-CVE-2026-46555-001.md: the page then shows that text, with the registry reference appended under it.