CVE-2026-77329
Tapo MCP keyless listeners allowed browser-driven smart-home control
mihai-dinculescu · tapo
First documented disclosure · Review checkpoint
Summary
A malicious page could reach an unauthenticated local or LAN MCP listener through DNS rebinding.
Severity and exploitation evidence
High · 8.8/10 · CVSS 4.0. Severity source.
Exploitation not established: Public evidence describes a weakness, source correction or controlled demonstration; malicious exploitation against users is not established.
Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.
How the weakness works
Host checks are disabled and bearer authentication is optional.
Conditions required
A running affected keyless listener, real Tapo credentials/devices, and a victim visiting an attacker page.
Potential impact
Device actuation and configured-camera snapshots; no Tapo credential or bearer-token disclosure is established.
Affected versions and configurations
0.3.1 through versions before 0.5.0; advisory lists through 0.4.0.
Fix and mitigation status
0.5.0.
Practical next steps
Upgrade; set TAPO_MCP_API_KEY and bind to loopback until upgraded. Use a narrow explicit host allowlist for LAN access.
Operating lesson
Pair network exposure with mandatory authentication and host validation.
Evidence and limits
Maintainer rates CVSS 4.0 5.3 Moderate; GitHub CNA rates CVSS 4.0 8.8 High. Preserve the distinct assessments. Fixed release restores Host allowlisting and refuses non-loopback startup without a key. CNA publication 2026-11-20 is distinct from the earliest reviewed public source. GitHub_M assessment: CVSS 4.0 8.8.
Sources
- GitHub_M CVE authority record
Primary source ·
- tapo original advisory
Primary source ·