Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessConnect to same network segment
-
DeliverySend crafted HTTP request with segmented body
-
ExploitBypass boundary validation in parser
-
ExecutionTrigger heap buffer overflow
-
ImpactCrash device process
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Heap buffer bounds checking
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Attacker must be on the same network segment as TP-Link Tapo C520WS v2.6. No authentication required. Attacker sends crafted HTTP payloads with malformed segmented request bodies to trigger heap buffer overflow in HTTP parsing loop, causing DoS. |
| Impact | While CVSS vector data is unavailable, the attack profile indicates moderate-to-high real-world risk for affected deployments. The attack vector is network-based and requires only network proximity (same segment), with no authentication required based on the description. The impact is limited to denial-of-service (process crash/hang) rather than code execution, which reduces severity compared to RCE-capable overflows. However, the combination of unauthenticated network access, low attack complexity (sending HTTP payloads), and reliable crash conditions makes this a practical DoS weapon against unpatched cameras in shared network environments (offices, retail locations, surveillance systems). The absence of EPSS and CVSS data prevents quantitative exploitation probability assessment, but the straightforward HTTP parsing attack surface and lack of authentication barriers suggest this could be relatively easy to exploit by an attacker with network access. The fact that a patch is already available suggests the vendor assessed this as a legitimate security concern warranting a fix release. |
| Exploit ScenarioDerived | An attacker on the same local network segment (e.g., office WiFi, compromised router) crafts a malicious HTTP request with a deliberately oversized or improperly formatted multi-part body. The attacker sends this payload to the Tapo C520WS HTTP server, triggering the vulnerable parsing loop to write beyond the heap buffer's boundaries. The heap corruption causes the camera process to crash or hang, rendering it unresponsive and breaking video feeds or management capabilities until the device is manually rebooted. No public exploit code is referenced in available intelligence, but the straightforward nature of HTTP buffer overflow attacks suggests proof-of-concept development is likely feasible for researchers with firmware analysis capabilities. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 02, 2026
Heap-based buffer overflow in TP-Link Tapo C520WS v2.6 allows unauthenticated network attackers to trigger denial-of-service by sending crafted HTTP payloads that bypass boundary validation during segmented request body parsing. The vulnerability exploits insufficient write-boundary verification in the HTTP parsing loop, causing heap memory corruption that crashes or hangs the device process. Patch is available from the vendor.
RemediationAI
Vendor-released patch is available per TP-Link advisory. Users should immediately check the Tapo C520WS firmware release notes and support pages (https://www.tp-link.com/us/support/download/tapo-c520ws/#Firmware-Release-Notes) to identify and download the patched firmware version that addresses CVE-2026-34119. Perform a firmware update via the Tapo app or device web interface to move to a version beyond v2.6 that includes the heap overflow fix. As a temporary mitigation for devices that cannot be patched immediately, restrict network access to the camera using firewall rules or network segmentation to limit exposure to attackers on the same network segment; however, this is not a substitute for patching and should only be used as a short-term measure while patches are being staged.
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 vulnerability resides in the HTTP request parsing component of the Tapo C520WS camera firmware (v2.6), specifically in the handler responsible for assembling multi-part or segmented HTTP request bodies. The root cause is CWE-122 (Heap-based Buffer Overflow), which occurs when the parser fails to continuously validate write boundaries as it appends external input to a heap-allocated buffer. Attackers can supply crafted payloads with improperly formatted or oversized segment data that causes the append operation to write beyond the allocated buffer's boundaries. The absence of persistent boundary checks between successive segment writes creates a classic heap overflow condition where attacker-controlled data overwrites adjacent heap structures, leading to memory corruption and process instability.
Know when Tapo C520Ws V2 6 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
Primary rating from Vendor (TPLink) · only source for this CVE.
CVSS VectorVendor: TPLink
Lifecycle Timeline
2DescriptionCVE.org
A heap-based buffer overflow vulnerability was identified in TP-Link Tapo C520WS v2.6 within the HTTP parsing loop when appending segmented request bodies without continuous write‑boundary verification, due to insufficient boundary validation when handling externally supplied HTTP input. An attacker on the same network segment could trigger heap memory corruption conditions by sending crafted payloads that cause write operations beyond allocated buffer boundaries. Successful exploitation causes a Denial-of-Service (DoS) condition, causing the device’s process to crash or become unresponsive.
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
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
A heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.
More in Tapo C520Ws V2 6
View allTP-Link Tapo C520WS v2.6 contains an authentication bypass in its HTTP-based DS configuration service that allows unauth
Denial-of-service vulnerability in TP-Link Tapo C520WS v2.6 camera allows adjacent network attackers to trigger buffer o
Heap-based buffer overflow in TP-Link Tapo C520WS v2.6 allows local network attackers to cause denial of service by send
Heap-based buffer overflow in TP-Link Tapo C520WS v2.6 allows remote attackers on the same network segment to trigger de
Stack-based buffer overflow in TP-Link Tapo C520WS v2.6 allows remote attackers to trigger denial-of-service by sending
EUVD-2026-18428
NVD
CVE.org
EPSS
Vulnrichment
VulDB
GitHub PoC
Exploit-DB