Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain access to local/Wi-Fi segment
-
DeliveryCraft malformed IPv4 fragments
-
ExploitFlood camera packet handler
-
ExecutionExhaust device memory/CPU
-
ImpactCamera unresponsive, video/recording lost
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V2 - Validation and Business Logic Resource allocation limits
MITRE ATT&CK
1 technique across 1 tactic: Impact The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to be on the adjacent network (AV:A) - the same local/Wi-Fi broadcast segment as the camera - and to send crafted IPv4 fragmented packets to the device; no authentication, credentials, or user interaction is needed (PR:N/UI:N), and no special camera feature or non-default configuration is called out as a prerequisite. The principal limiting factor is the adjacency requirement: this cannot be exploited directly from the internet, so the attacker must first obtain local network access (compromised LAN host, shared/guest Wi-Fi, or rogue device). The impact is also self-limiting - availability only (VA:H, confidentiality/integrity unaffected) and described by the vendor as a temporary, recoverable condition, so the camera typically resumes once the malicious traffic stops. |
| Impact | The supplied CVSS 4.0 vector (AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H, base 7.1) is internally consistent with the description: adjacent attack surface, low complexity, no privileges or user interaction, and an availability-only impact (VA:H) with no confidentiality or integrity loss. There is no EPSS score, no SSVC decision, and no POC provided, and the CVE is not in CISA KEV, so there is no evidence of active or automatable exploitation. The most important limiting factor is AV:A - the attacker must be on the same local/Wi-Fi segment as the camera, not anywhere on the internet, which sharply narrows real-world reach to attackers who already have local network access (e.g., a compromised LAN, shared Wi-Fi). Net assessment: a genuine but bounded risk - meaningful for availability-sensitive surveillance use, yet not an internet-wide mass-exploitation threat, and the impact is a temporary, recoverable outage rather than data compromise or code execution. |
| Exploit ScenarioDerived | An attacker who has gained access to the same Wi-Fi network as the camera - for example via a weak Wi-Fi password or another compromised device on the LAN - sends a stream of crafted, malformed IPv4 fragmented packets to the Tapo C200 v3. The camera's packet handling logic exhausts memory or CPU reassembling the fragments and becomes unresponsive, dropping live video and recording for the duration of the attack. No exploit code is publicly known at time of analysis, but the low attack complexity (AC:L) and absence of any authentication or user interaction make the technique straightforward for a locally positioned adversary. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 24, 2026
Remote denial-of-service in the TP-Link Tapo C200 v3 home security camera allows an unauthenticated attacker on the adjacent network to crash or destabilize the device by sending malformed IPv4 fragmented packets. Exploitation drives excessive resource consumption (CWE-770) and renders the camera unresponsive, causing intermittent loss of live video monitoring and recording. No public exploit has been identified at time of analysis, and the issue is not listed in CISA KEV; TP-Link, who reported it, has released a firmware fix.
RemediationAI
Patch available per vendor advisory: update the Tapo C200 v3 to the latest firmware listed in TP-Link's release notes (https://www.tp-link.com/us/support/download/tapo-c200/v3/#Firmware-Release-Notes or the EN mirror), as an exact fixed build number was not provided in the input - confirm the current version against those release notes before and after updating. TP-Link's supporting advisory is at https://www.tp-link.com/us/support/faq/5143/. Because the attack is adjacent-network only, effective compensating controls until patched are: isolate the camera on a dedicated IoT VLAN or guest SSID to remove untrusted devices from its broadcast/local segment (trade-off: requires router/AP support and may complicate app discovery and local streaming), and restrict Wi-Fi access with strong WPA2/WPA3 credentials to limit who can reach the device at layer 2. Network-layer fragment filtering is impractical on consumer gear, so segmentation is the primary stopgap; note these controls reduce exposure but do not eliminate the flaw for an attacker already on the same segment.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw lives in the camera's network packet handling logic, specifically its reassembly/handling of fragmented IPv4 datagrams. IPv4 fragmentation splits oversized packets into smaller fragments that the receiving stack must buffer and reassemble; without strict limits on the number, size, or rate of in-flight fragments, an attacker can force the device to allocate memory or CPU faster than it can reclaim them. This maps directly to CWE-770 (Allocation of Resources Without Limits or Throttling) - the root cause is missing bounds on resources consumed during fragment processing on a resource-constrained embedded IoT device. The affected component is identified by CPE cpe:2.3:a:tp-link_systems_inc.:tapo_c200_v3, TP-Link's Tapo C200 hardware version 3 Wi-Fi pan/tilt camera.
Know when Tapo C200 V3 gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Adjacent-network attacker (AV:A) sends fragments with no auth or interaction (AC:L/PR:N/UI:N); impact is availability-only (A:H) with no confidentiality or integrity loss and no scope change.
Primary rating from Vendor (TPLink).
CVSS VectorVendor: TPLink
DescriptionCVE.org
A 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.
Executive ViewAI
TP-Link Tapo C200 v3 cameras are vulnerable to remote denial-of-service attacks that can disable physical security monitoring capabilities. Attackers with adjacent network access can render cameras inoperable, creating gaps in surveillance coverage and potentially compromising incident response capabilities.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
EUVD-2026-39026
GHSA-25hh-rw6j-95ch
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB