CVE-2026-12760
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 · uneditedA denial-of-service (DoS) vulnerability has been identified in Tapo C200 v3 in the network packet handling logic due to improper handling of IPv4 fragmented packets. An unauthenticated adjacent attacker can send crafted packets to cause excessive resource consumption, leading to instability of the device.Successful exploitation can remotely trigger a temporary denial-of-service condition, causing the camera to become unresponsive and resulting in intermittent loss of video monitoring and recording.
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 · moderate confidenceThe Tapo C200 v3 camera has a denial-of-service vulnerability in its network packet handling logic. The device improperly handles IPv4 fragmented packets, allowing an unauthenticated adjacent attacker to send crafted packets that cause excessive resource consumption, leading to device instability and unresponsiveness.
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.3.3= 1.3.4= 1.3.5= 1.3.7= 1.3.9= 1.3.11= 1.3.13= 1.3.14= 1.3.15= 1.4.1= 1.4.2CVSS 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.
-
Identify the device modelLocate the device on your network or physically inspect it to confirm it is a Tapo C200 v3 camera. Check the device label, web interface, or mobile app for the exact model number.Affected if The device is not a Tapo C200 v3, then this CVE does not apply.
-
Check the installed firmware versionAccess the Tapo mobile app, the camera's web interface, or check the device settings to view the current firmware version. Compare this version against the affected list: 1.3.3, 1.3.4, 1.3.5, 1.3.7, 1.3.9, 1.3.11, 1.3.13, 1.3.14, 1.3.15, 1.4.1, 1.4.2.Affected if The installed firmware version matches one of the versions listed in the affected products.
-
Verify network accessibility of the deviceConfirm that the camera is reachable on your network. Use ping or a network scanner to verify the device is online and responding to network traffic.Affected if The device is powered on and connected to the network, making it reachable for an adjacent attacker to send packets.
-
Assess network exposure to adjacent attackersDetermine if the device is on a network segment accessible to untrusted users. Check if the device is behind a firewall or NAT that limits access to trusted devices only.Affected if The device is on a shared or untrusted network segment where unauthenticated adjacent attackers can send IPv4 packets to the device.
The device is affected if it is a Tapo C200 v3 running any of the listed firmware versions and is reachable on a network where adjacent attackers can send IPv4 fragmented packets to it.
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-provided firmware update for the Tapo C200 v3 when available. Until then, network segmentation and firewall rules can limit the attack surface from adjacent network attackers.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12760 — 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-12760 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