CVE-2026-1871
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedTP-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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA stack-based buffer overflow vulnerability exists in the RTSP authentication handling of TP-Link Tapo C200 v5 cameras. The flaw stems from improper validation of Authorization header field lengths, allowing an attacker to send a crafted authentication request with an oversized header value that overflows the stack buffer. This causes the RTSP service process to crash, triggering an automatic system reboot and resulting in denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0.5= 1.0.12= 1.0.13= 1.0.17= 1.1.4= 1.1.8= 1.2.3= 1.3.1= 1.3.3= 1.3.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm device model is TP-Link Tapo C200Locate the device label on the physical camera or access the Tapo app or web interface to verify the device model number.Affected if Device is not a TP-Link Tapo C200, then not affected.
-
Check firmware versionIn the Tapo app, go to Device Settings > Device Info, or access the camera's web UI and look for the firmware version field. Compare the installed version against the affected list: 1.0.5, 1.0.12, 1.0.13, 1.0.17, 1.1.4, 1.1.8, 1.2.3, 1.3.1, 1.3.3, 1.3.5.Affected if Firmware version matches one of the listed versions, then vulnerable to this CVE.
-
Verify RTSP service is enabledIn the Tapo app, go to Device Settings > Storage > SD Card, or access the camera web interface and check the RTSP settings. Look for an option to enable RTSP streaming.Affected if RTSP service is disabled, the vulnerability is not exploitable even on a vulnerable firmware version.
-
Check RTSP port accessibilityUse a network scanner or run 'nc -zv <camera_ip> 554' or 'nmap -p 554 <camera_ip>' from a computer on the same network to verify port 554 (standard RTSP port) is open and responding.Affected if RTSP port 554 is accessible from an untrusted network, an attacker could potentially send malicious authentication requests.
You are affected if you have a TP-Link Tapo C200 running any of the listed firmware versions with RTSP service enabled and accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the vendor-supplied firmware update for TP-Link Tapo C200 v5 once available. As an interim measure, restrict network access to the RTSP service to trusted IP addresses or place the device behind a firewall to reduce attack surface.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1871 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-1871 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data