# CVE-2026-77329 - Tapo: DNS rebinding reaches unauthenticated Tapo MCP smart-home controls

DevFeed: [CVE-2026-77329 - Tapo: DNS rebinding reaches unauthenticated Tapo MCP smart-home controls](<https://devfeed.tech/articles/cve-2026-77329-tapo-dns-rebinding-reaches-unauthenticated-tapo-mcp-smart-home-controls-146412.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-77329>)

Author: CVEFEED.io; github.com

Published: 2026-11-20T17:18:26Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [smartdevices](<https://devfeed.tech/topics/smartdevices.md>), [Domain Name System (DNS)](<https://devfeed.tech/topics/dns-resolution-process.md>)

Tags: [api-key](<https://devfeed.tech/tags/api-key.md>), [browser](<https://devfeed.tech/tags/browser.md>), [cameras](<https://devfeed.tech/tags/cameras.md>), [cve-2026-77329](<https://devfeed.tech/tags/cve-2026-77329.md>), [devices](<https://devfeed.tech/tags/devices.md>), [dns](<https://devfeed.tech/tags/dns.md>), [dns-rebinding](<https://devfeed.tech/tags/dns-rebinding.md>), [exploitation](<https://devfeed.tech/tags/exploitation.md>), [http](<https://devfeed.tech/tags/http.md>), [interfaces](<https://devfeed.tech/tags/interfaces.md>), [lan](<https://devfeed.tech/tags/lan.md>), [malicious](<https://devfeed.tech/tags/malicious.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [mihai-dinculescu](<https://devfeed.tech/tags/mihai-dinculescu.md>), [optional](<https://devfeed.tech/tags/optional.md>), [python](<https://devfeed.tech/tags/python.md>), [running](<https://devfeed.tech/tags/running.md>), [rust](<https://devfeed.tech/tags/rust.md>), [smart-home](<https://devfeed.tech/tags/smart-home.md>), [tapo](<https://devfeed.tech/tags/tapo.md>)

## AI overview

From versions 0.3.1 to before 0.5.0, Tapo's Streamable HTTP MCP server could accept DNS-rebound browser requests without Host or Origin validation when TAPO_MCP_API_KEY was unset. If the listener was running with Tapo credentials and devices configured, a victim's visit to a malicious site could let an attacker invoke tools such as control_device or take_snapshot. The unauthenticated path does not apply when an API key is set; exploitation also requires victim interaction. The issue is fixed in 0.5.0.

## Source excerpt

CVE ID :CVE-2026-77329 Published : Nov. 20, 2026, 5:18 p.m. | 18 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 details, affected products, timeline, and more...