CVE-2026-1871TP-Link Tapo C200 v5 contains a stack-based buffer overflow flaw in RTSP authentication handling due to improper validation of Authorization header field lengths, which can be triggered by a crafted…
Updated under an hour ago ()
Does this affect you?
It affects tp-link tapo_c200_firmware. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
TP-Link Tapo C200 v5 contains a stack-based buffer overflow flaw in RTSP authentication handling due to improper validation of Authorization header field lengths, which can be triggered by a crafted authentication request. Successful exploitation causes the affected RTSP core service process to crash and triggers an automatic system reboot, resulting in a denial of service (DoS) condition. This prevents legitimate users from accessing the camera’s live video stream or management interface until the service restarts.
- CVSS
- 6.5 MEDIUM (v3.1, NVD)CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Weakness (CWE)
- CWE-121
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Not given
- NVD analysis
- Analyzed
- Record last updated
- Jul 22, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
tp-link tapo_c200_firmware tp-link:tapo_c200_firmware | 1.0.5; 1.0.12; 1.0.13; 1.0.17; 1.1.4; 1.1.8; 1.2.3; 1.3.1; and 2 more ranges | NVD |
References
- https://www.tp-link.com/en/support/download/tapo-c200/v5/#Firmware-Release-Notesrelease-notes
- https://www.tp-link.com/kr/support/download/tapo-c200/#Firmware-Release-Notesrelease-notes
- https://www.tp-link.com/us/support/download/tapo-c200/v5/#Firmware-Release-Notesrelease-notes
- https://www.tp-link.com/us/support/faq/5113/vendor-advisory
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.