Device-process crash via HTTP POST heap overflow
Published Apr 2, 2026 · Updated Apr 2, 2026
Heap-based buffer overflow in TP-Link Tapo C100/C101 5 and C520WS 2.6 allows remote attackers on the same network to crash device processes. The HTTP POST body parser dynamically allocates a heap buffer but fails to validate its remaining capacity before writing externally supplied body data. Crafted requests can therefore write past the allocation and leave an affected camera process crashed or unresponsive; no authentication is required, but the attacker must share its network segment.
Summary
What happened
Heap-based buffer overflow in TP-Link Tapo C100/C101 5 and C520WS 2.6 allows remote attackers on the same network to crash device processes. The HTTP POST body parser dynamically allocates a heap buffer but fails to validate its remaining capacity before writing externally supplied body data. Crafted requests can therefore write past the allocation and leave an affected camera process crashed or unresponsive; no authentication is required, but the attacker must share its network segment.
The record
- CVE
- CVE-2026-34118
- Published
- Apr 2, 2026
- Updated
- Apr 2, 2026
- Vendor
- TP-Link Systems Inc.
- Product
- Tapo C520WS
- Classifications
- CWE-122, T1499.004
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 2, 2026CVE publishedPublication date reported by the CVE source.
- Apr 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.2.4 Build 260326 Rel.24666n
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo