CVE Feed
8.8 High

Tapo provides Rust and Python APIs and an MCP server for TP-Link Tapo smart devices.

CVE-2026-77329

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.

Part of the AI stack

This affects Model Context Protocol, in MCP & tool servers.

Assessment

CVSS
8.8 (v4.0)
Severity
High
Known exploited
Not listed in CISA KEV
Exploit availability
Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
Published
20 November 2026
Last updated
20 November 2026
Assigner
GitHub_M

CVSS vectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N

At the source

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept
Before you submit *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-77329