← All advisories
CVE-2026-77329highAgent hijacking2026-11-20

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.

01.

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.

02.

How to check

  1. Check the tapo-mcp image tag or binary version.
  2. Check whether TAPO_MCP_API_KEY is set for the container or service.
03.

How to fix

  1. Upgrade tapo-mcp to 0.5.0 or later.
  2. 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
04.

Sources

Related on VibeVulns
More advisories for this tool
The weekly email

One email a week. Only what changed.

Every new security hole in AI coding tools, MCP servers, app builders and the stacks they generate (Next.js, Supabase, Node, PHP), each with how to check your app and the fix. No roundups of things you already read.

Free, one email a week. Read the latest issue first if you like. One-click unsubscribe in every email. We never sell or share addresses.