What’s Vulnerable › Vulnerabilities
CVE-2026-102369: Unauthenticated Remote Code Execution via MacTool Command Injection in TP-Link Tapo C120 & C200
- Severity: high (CVSS 8.7 v4.0)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.3% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2026-10-01 · updated 2026-10-01
- Weakness: CWE-287
Description
Tapo C120 v1 and C200 V5 do not adequately protect login challenge data or sanitize attacker-controlled input processed by the MacTool handler. An unauthenticated attacker on the same local network can replay login challenge data to obtain an administrative session, enable a privileged service that becomes accessible after a reboot, and submit crafted input to execute arbitrary commands within the device management process. Successful exploitation may allow arbitrary command execution on the camera and compromise the confidentiality, integrity, and availability of the affected device. Exploitation requires access from the same local network, replay of the login challenge data, activation of the privileged service, and a device reboot.
Affected products
- TP-Link Systems Inc. Tapo C120 v1: before V1_1.9.4 Build 260813 Rel.79754n — fixed in V1_1.9.4 Build 260813 Rel.79754n
- TP-Link Systems Inc. Tapo C200 v5: before V5_1.4.6 Build 260709 Rel.27675n — fixed in V5_1.4.6 Build 260709 Rel.27675n
How to fix
Upgrade to a fixed version: TP-Link Systems Inc. Tapo C120 v1 V1_1.9.4 Build 260813 Rel.79754n; TP-Link Systems Inc. Tapo C200 v5 V5_1.4.6 Build 260709 Rel.27675n. Check the vendor advisory for mitigations.
References
- https://www.tp-link.com/en/support/download/tapo-c120/v1.26/#Firmware-Release-Notes
- https://www.tp-link.com/en/support/download/tapo-c200/v5/#Firmware-Release-Notes
- https://www.tp-link.com/us/support/download/tapo-c120/v1.26/#Firmware-Release-Notes
- https://www.tp-link.com/us/support/download/tapo-c200/v5/#Firmware-Release-Notes
- https://www.tp-link.com/us/support/faq/5321/
Get alerted when CVE-2026-102369 or the next vulnerability affects your stack