CVE-2026-77329 - Tapo: DNS rebinding reaches unauthenticated Tapo MCP smart-home controls
First reported Fri, 20 Nov 2026 · 2 d ago
{ "Source": "CVE FEED", "Title": "CVE-2026-77329 - Tapo: DNS rebinding reaches unauthenticated Tapo MCP smart-home controls", "Content": " CVE ID : CVE-2026-77329 Published : Nov. 20, 2026, 5:18 p.m. | 12 minutes ago Description : 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 disable_allowed_hosts() without replacement Host or Origin validation, while TAPO_MCP_API_KEY 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 control_device for smart-device actuation and take_snapshot for configured cameras. Deployments with TAPO_MCP_API_KEY 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. Severity: 8.8 | HIGH Visit the link for more details, such as CVSS det
Vulnerability: CVE-2026-77329
Sources (1)
- Telegram @CVEDetector — { "Source": "CVE FEED", "Title": "CVE-2026-77329 - Tapo: DNS rebinding reaches unauthenticated Tapo MCP smart-home contr
Sell to companies like this, at the right moment
BugzyCRM finds the right contact and drafts a sourced email within hours of an incident.