Answer in brief
CVE-2026-34118 records a Unknown severity vulnerability in Heap-based Buffer Overflow Vulnerability Leading to Denial-of-Service in TP-Link Tapo C100, C101 & C520WS. The current sources do not mark it as known exploited. The current feed maps TP Link Systems Inc./Tapo C100 v5 (generic), TP Link Systems Inc./Tapo C101 v5 (generic), TP-Link Systems Inc./Tapo C520WS v2.6 (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps TP Link Systems Inc./Tapo C100 v5 (generic), TP Link Systems Inc./Tapo C101 v5 (generic), TP-Link Systems Inc./Tapo C520WS v2.6 (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| TP Link Systems Inc./Tapo C100 v5generic | >=0 <1.5.4 Build 260528 Rel.11462n | 1.5.4 Build 260528 Rel.11462n |
| TP Link Systems Inc./Tapo C101 v5generic | >=0 <1.5.4 Build 260528 Rel.11462n | 1.5.4 Build 260528 Rel.11462n |
| TP-Link Systems Inc./Tapo C520WS v2.6generic | >=0 <1.2.4 Build 260326 Rel.24666n | 1.2.4 Build 260326 Rel.24666n |
Published upstream
Apr 2, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 19, 2026
A heap-based buffer overflow vulnerability was identified in TP-Link Tapo C100/C101 v5, C520WS v2.6 in the HTTP POST body parsing logic due to missing validation of remaining buffer capacity after dynamic allocation, 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.
Quoted source text, attributed separately from HOL analysis.