CVE-2026-77329: Tapo MCP server without an API key let a malicious website use DNS rebinding to control TP-Link Tapo devices and take camera snapshots (fixed 0.5.0)
tapo-mcp, the MCP server in the mihai-dinculescu/tapo project for TP-Link Tapo smart devices, turned off rmcp's loopback-only Host allowlist for its Streamable HTTP transport (disable_allowed_hosts()) without adding its own Host or Origin check, and TAPO_MCP_API_KEY was optional on a listener that can bind to all interfaces. From 0.3.1 until 0.5.0, a website the victim visited could use DNS rebinding to send same-origin requests to a local or LAN Tapo MCP listener running without an API key, then call tools such as control_device to switch devices and take_snapshot to capture images from configured cameras. Deployments with TAPO_MCP_API_KEY set are not affected by the unauthenticated path. Fixed in 0.5.0.
What it is
Vulnerable code: tapo-mcp/src/server.rs calls StreamableHttpServerConfig::default().disable_allowed_hosts() so the server is reachable over the LAN, relying on bearer auth that tapo-mcp/src/lib.rs makes optional.
Exploitation needs a running listener configured with real Tapo credentials and devices, no API key, and the victim visiting the attacker's site.
Affected: tapo-mcp 0.3.1 to 0.4.0 (the documented container image ghcr.io/mihai-dinculescu/tapo-mcp). tapo-mcp v0.5.0 was released on 11 July 2026; NVD published the CVE on 20 November 2026.
How to check
- Check the tapo-mcp image tag or binary version.
- Check whether TAPO_MCP_API_KEY is set for the container or service.
How to fix
- Upgrade tapo-mcp to 0.5.0 or later.
- Always set TAPO_MCP_API_KEY, and don't publish the port beyond the machines that need it.
docker ps --format '{{.Image}} {{.Ports}}' | grep -i tapo-mcp
docker inspect <container> | grep -c TAPO_MCP_API_KEY Sources
- criticalCVE-2026-77359: Jupyter MCP Server's /api/connect and /api/stop routes skipped the token and Origin checks, so a website or network caller could repoint it to an attacker's Jupyter backend (fixed 1.0.3)
- highCVE-2026-77283: obsidian-sync-mcp in no-auth mode let any website use DNS rebinding to read, overwrite and delete your Obsidian vault notes (fixed 0.5.7)
- criticalMalicious npm package @guicai777/mcp-doctor posed as an MCP diagnostic tool and dropped a hidden Windows executable, with a README telling users to run mshta (MAL-2026-20295)
- criticalMalicious npm packages posing as AI SDKs and MCP servers: character-ai-sdk, char-ai-sdk, @mibbp/agent-observer, mrnima-openai-chatgpt-bot and @fdcasj_dfew/md-doc-mcp
- criticalCVE-2026-76807: Doist's official Todoist MCP HTTP server let any website use DNS rebinding to read, create and delete your Todoist data (fixed 10.3.3)
- criticalMalicious AI agent and MCP packages: mcp-aevo-server (PyPI) steals Aevo trading keys and wallet private keys; vamp-mcp, tsc-ai and @tnhorg/agent-skills (npm) flagged as malware