AI Stack Alert High CVE-2026-77329 For CISO, SOC / IR, AppSec, AI Eng AI-assisted
CVE-2026-77329: Tapo MCP server DNS rebinding allows unauthenticated device control when no API key is set
Tapo, a set of Rust and Python APIs and an MCP server for TP-Link Tapo smart devices, versions 0.3.1 through 0.5.0 skip Host or Origin validation in its Streamable HTTP implementation. When TAPO_MCP_API_KEY is not set, a malicious website can use DNS rebinding to send requests to a local or LAN Tapo MCP listener, invoking tools such as control_device and take_snapshot. The issue is fixed in version 0.5.0.
Why it matters
Organizations running the Tapo MCP listener without an API key on a reachable network expose smart-device actuation and camera snapshots to any visitor of a malicious web page. CVSS base score is 8.8.
Do this
- Upgrade the tapo-mcp server to version 0.5.0 or later.
- Set TAPO_MCP_API_KEY on every running Tapo MCP listener until the upgrade is complete.
- Restrict the listener to localhost or a trusted management network instead of binding to all interfaces.
- Review logs for unexpected control_device or take_snapshot calls on Tapo MCP hosts.
Exploit Clock
No signals yet
- No exploitation signals yet
Signals
- NoCISA KEV
- 8.8CVSS
- NoPublic PoC
- 37/100Priority
- 85%Confidence
Evidence
“From 0.3.1 until 0.5.0, the Streamable HTTP implementation in tapo-mcp/src/server.rs calls disable_allowed_hosts() without replacement Host or Origin validation”
“Deployments with TAPO_MCP_API_KEY set are not affected by the unauthenticated path”
“This issue is fixed in version 0.5.0.”
Sources
Affected / related
Tapo MCP server (tapo-mcp), tapo, TP-Link, DNS rebinding
Published 2026-11-20 17:18 UTC · updated 2026-11-20 18:35 UTC · AI-assisted summary, checked against quoted sources · How we score