On this page
CVE Details
- Protection status: Protected by Atomicorp rules · About protection statuses
- CVE: CVE-2026-77329
- Name: Tapo: DNS rebinding reaches unauthenticated Tapo MCP smart-home controls
- Severity: High
- CVSS: 8.8 (v4.0) (High)
- CVSS version: 4.0
- CVSS source: GitHub_M CNA
- CVSS vector:
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X- Attack vector: Network
- Attack complexity: Low
- Attack requirements: Present
- Privileges required: None
- User interaction: Passive
- Vulnerable-system confidentiality: High
- Vulnerable-system integrity: High
- Vulnerable-system availability: None
- Subsequent-system confidentiality: High
- Subsequent-system integrity: High
- Subsequent-system availability: None
- Safety: Not defined
- CWE: CWE-346 , CWE-350
- Vendor: mihai-dinculescu
- Vulnerable product: tapo
- CVE published: 2026-11-20
- CVE last modified: 2026-11-20
- Latest Update: 2026-11-21
- Selected Rule IDs observed: 390719
- Matching rules: 1; rules with blocking actions: 1
- Would-block Rule IDs: 390719
- Request surfaces inspected: Request headers
Technical vulnerability details · CVSS assessments, exploit evidence & CPE data
CVSS assessments
CVSS v4.0 · security-advisories@github.com
- Base score: 8.8
- Base severity: HIGH
- Assessment type: Secondary
- Source identifier: security-advisories@github.com
- Full vector:
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X- Attack vector: Network
- Attack complexity: Low
- Attack requirements: Present
- Privileges required: None
- User interaction: Passive
- Vulnerable-system confidentiality: High
- Vulnerable-system integrity: High
- Vulnerable-system availability: None
- Subsequent-system confidentiality: High
- Subsequent-system integrity: High
- Subsequent-system availability: None
- Safety: Not defined
- Exploit maturity: Not scored
Exploitability and impact subscores describe the vulnerability’s technical characteristics. Exploit maturity describes the reported state of exploitation; these are separate measures.
Assessment source: NVD record (opens in a new tab) · CVE record (opens in a new tab)
CISA SSVC assessments
These are CISA’s published decision points at the assessment time. They are not a complete organization-specific prioritization decision.
- Provider: CISA ADP
- Provider identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
- SSVC version: 2.0.3
- Role: CISA Coordinator
- Assessment timestamp: 2026-11-20T20:58:47.675566Z
- Exploitation: poc
- Automatable: no
- Technical Impact: total
- Source: CISA ADP in the CVE record (opens in a new tab)
Vulnerable CPE configurations
No vulnerable CPE configurations are supplied in the current NVD record. See the affected-product information and vendor guidance on this page.
Vulnerability 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.
Recommended Actions
Maintain the observed Atomicorp protections. Keep your Atomicorp commercial rules current and confirm that the selected observed rules (390719 ) have not been locally disabled. Atomicorp commercial rules are enabled by default. If you use Atomic WAF, review the applicable policy and rule settings.
Apply the vendor’s remediation. WAF protection is defense in depth and does not replace upgrading or following the affected vendor’s guidance.
- Affected versions: mihai-dinculescu tapo version >= 0.3.1, < 0.5.0.
- No specific CNA/vendor solution or workaround is included in the current CVE Record (opens in a new tab) . Review the vendor’s security advisories and supported-release guidance before making changes.
Validate after changes. Confirm rule updates are current, review WAF events for the affected application, and test application behavior after vendor upgrades, mitigations, or local policy changes.
Research Notes
Atomicorp WAF protections are designed around attack techniques and exploit behaviors, allowing existing protections to apply across multiple vulnerabilities without requiring a unique rule for every CVE.
Public Vulnerability References
- NVD (opens in a new tab)
- CVE Record (opens in a new tab)
- CVE authority reference: https://github.com/mihai-dinculescu/tapo/commit/cb9c5d4372bddfa11f19dc653a27c9aa4fa92833 (opens in a new tab)
- CVE authority reference: https://github.com/mihai-dinculescu/tapo/releases/tag/tapo-mcp-v0.5.0 (opens in a new tab)
- CVE authority reference: https://github.com/mihai-dinculescu/tapo/security/advisories/GHSA-2cwc-6wwp-62q6 (opens in a new tab)
Test or Research Source
- Source: Atomicorp AI Research Framework
- Tags: cve, derived, ssrf, waf-probe
Research Note Context
This research note documents exploit-technique analysis associated with this vulnerability and references Atomicorp WAF protections observed during engineering review, testing, or validation activities.
Atomicorp security controls are generally designed to identify and mitigate attack techniques and exploit behaviors rather than individual CVE identifiers. As a result, protections developed for one vulnerability may also apply to related attack variants and future vulnerabilities using similar techniques.
Learn More
Atomicorp develops commercially supported security technologies for web applications, servers, endpoints, workloads, and legacy enterprise platforms.
Organizations interested in protecting systems against exploit techniques associated with vulnerabilities such as this one can learn more about:
- Atomic ModSecurity Rules: commercially maintained WAF rules for ModSecurity deployments, including protections for web attacks, bots, scanners, malware, exploitation attempts, and emerging vulnerability classes.
- Atomic WAF: an enterprise web application firewall with Atomicorp rules, centralized management, reporting, authentication controls, and operational tooling.
- Atomic ModSecurity Integrator: a special licensing option for MSPs, MSSPs, OEMs, VARs, reverse proxy providers, and other integrators who want to incorporate Atomicorp ModSecurity rule technology into their own products or services.
- Atomic OSSEC: an enterprise OSSEC-based intrusion detection, compliance, and security monitoring platform.
- Atomic Protector: workload protection for Linux, web, cloud, data center, and hybrid environments.
For additional information, product evaluations, or technical discussions, visit https://www.atomicorp.com/ or https://modsecurity.io/ (opens in a new tab) .