CVE-2026-77329
Received Received - Intake

DNS Rebinding Attack in Tapo MCP Server Allows Unauthenticated Device Control

Vulnerability report for CVE-2026-77329, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-20

Last updated on: 2026-11-20

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-20
Last Modified
2026-11-20
Generated
2026-11-20
AI Q&A
2026-11-20
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
tp-link tapo From 0.3.1 (inc) to 0.5.0 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-346 The product does not properly verify that the source of data or communication is valid.
CWE-350 The product performs reverse DNS resolution on an IP address to obtain the hostname and make a security decision, but it does not properly ensure that the IP address is truly associated with the hostname.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects Tapo's Rust and Python APIs and MCP server for TP-Link Tapo smart devices. Between versions 0.3.1 and 0.5.0, the Streamable HTTP implementation lacks proper Host or Origin validation after calling disable_allowed_hosts(). Without an API key, the listener can bind to all interfaces, allowing a malicious website to use DNS rebinding to send same-origin requests to the victim's local or LAN Tapo MCP listener. This enables attackers to invoke exposed tools like control_device for device actuation or take_snapshot for cameras.

Detection Guidance

Check if tapo-mcp version is between 0.3.1 and 0.5.0. Run 'cargo show tapo-mcp' or 'pip show tapo-mcp' to verify version. Inspect server logs for HTTP requests without Host or Origin headers.

Impact Analysis

If you run Tapo MCP without an API key and interact with a malicious website, an attacker could take control of your smart devices or access camera snapshots. Exploitation requires the listener to be running with valid Tapo credentials and devices, and the victim to interact with the attacker's site. Deployments with TAPO_MCP_API_KEY set are not vulnerable.

Mitigation Strategies

Upgrade tapo-mcp to version 0.5.0 or later. Ensure TAPO_MCP_API_KEY is set to prevent unauthenticated access. Disable the MCP server if not in use. Monitor network traffic for unusual requests to local interfaces.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-77329. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...