CVE-2026-77329: Tapo: DNS rebinding reaches unauthenticated Tapo MCP smart-home controls
Tapo provides Rust and Python APIs and an MCP server for TP-Link Tapo smart devices. From 0.3.1 until 0.5.0, the Streamable HTTP implementation in tapo-mcp/src/server.rs calls disableallowedhosts() without replacement Host or Origin validation, while TAPOMCPAPIKEY remains optional for a listener that can bind to all interfaces. A malicious website can use DNS rebinding to send same-origin browser requests to the victim's local or LAN Tapo MCP listener when it runs without an API key. The attacker can invoke exposed tools including controldevice for smart-device actuation and takesnapshot for configured cameras. Deployments with TAPOMCPAPIKEY set are not affected by the unauthenticated path, and exploitation requires a running listener configured with real Tapo credentials and devices, plus victim interaction with the malicious site. This issue is fixed in version 0.5.0.
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 0.5.0 - Configuration
Set TAPO_MCP_API_KEY to require authentication for the listener.
Tapo MCP listener TAPO_MCP_API_KEY = set