CVE intelligence and bounded remediation

CVE-2026-1871 — Tp-Link Tapo C200 Firmware security vulnerability

High CVSS 7.1

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.

Severity
High
CVSS
7.1 (4.0)
Published
2026-06-02
CISA KEV
Not currently listed
Ecosystem
operating-system
Weaknesses
CWE-121

Affected products

  • tp-link / tapo_c200_firmware / 1.0.5
  • tp-link / tapo_c200_firmware / 1.0.12
  • tp-link / tapo_c200_firmware / 1.0.13
  • tp-link / tapo_c200_firmware / 1.0.17
  • tp-link / tapo_c200_firmware / 1.1.4
  • tp-link / tapo_c200_firmware / 1.1.8

Showing 6 representative product identities from 10 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

Buffer bounds, memory safety, and memory corruption

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Identify affected native-code versions, build flags, architectures, parsers, codecs, drivers, and input paths in all shipped artifacts.
  • Determine whether untrusted data reaches the affected routine and the process privilege, sandbox, and network exposure.
  • Confirm statically linked, vendored, firmware, and platform-provided copies, not only package-manager records.

Remediate safely

  • Apply the maintained upstream correction or replace the affected component, then rebuild every dependent artifact from clean inputs.
  • Adopt bounds-checked interfaces, validated sizes and integer conversions, clear ownership, and memory-safe components where practical.
  • Enable supported compiler and runtime hardening and add sanitized tests and fuzz regression seeds derived from non-weaponized fixtures.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.