CVE-2026-77329

Tapo: DNS rebinding reaches unauthenticated Tapo MCP smart-home controls

State
Published
Severity
8.8 High
Published
Nov 20, 2026
Updated
Nov 20, 2026
Reserved
Aug 20, 2026

Read the record on cve.org

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.

Scores

CVSSScoreVectorSource
4.08.8 HighCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:NGitHub_M

Weaknesses

  • CWE-346 Origin Validation Error
  • CWE-350 Reliance on Reverse DNS Resolution for a Security-Critical Action

Affected Products

ProductVersions
tapomihai-dinculescu
  • >= 0.3.1, < 0.5.0Affected

References

Every record here comes from the CVE Program's CVE List. © 1999-2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.

© 2026 NVIDIA, the NVIDIA logo, and NVIDIA Inception are trademarks and/or registered trademarks of NVIDIA Corporation in the U.S. and other countries.