Quick answers
- Is CVE-2026-1871 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-1871 being exploited in the wild.
- How severe is CVE-2026-1871?
- Informational severity, with a CVSS score of 7.1, published 2 June 2026.
- Which products and versions are affected?
- TP-Link Tapo C200 v5.
- Is there a fix for CVE-2026-1871?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-1871 attacked?
- It is attacked from the adjacent network, in a network appliance.
- Am I affected by CVE-2026-1871?
- Check whether you run TP-Link Tapo C200 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A stack-based buffer overflow vulnerability exists in the RTSP core service of the TP-Link Tapo C200 v5. The flaw is caused by improper validation of the length of the 'Authorization' header field during RTSP authentication. An attacker on the same local network can trigger this overflow by sending a crafted authentication request. Successful exploitation results in the RTSP process crashing, which triggers an automatic system-wide reboot, effectively creating a denial of service (DoS) condition for the camera's primary functions. Firmware updates are typically available through the Tapo mobile application.
Affected products
- TP-Link Tapo C200 v5
Timeline
- 2026-06-02: disclosed: CVE published by TP-Link via NVD