Device reboot via HTTP path expansion overflow
Published Apr 2, 2026 · Updated Apr 2, 2026
Classic buffer overflow in TP-Link Tapo C520WS v2.6 before 1.2.4 Build 260326 Rel.24666n allows remote attackers to reboot the device. The HTTP request path parser checks the raw path length but normalizes it into a larger path without rechecking the destination buffer, causing memory corruption. No authentication or user interaction is required, but the attacker must reach the camera from the same network segment; exploitation interrupts service or reboots the device.
Summary
What happened
Classic buffer overflow in TP-Link Tapo C520WS v2.6 before 1.2.4 Build 260326 Rel.24666n allows remote attackers to reboot the device. The HTTP request path parser checks the raw path length but normalizes it into a larger path without rechecking the destination buffer, causing memory corruption. No authentication or user interaction is required, but the attacker must reach the camera from the same network segment; exploitation interrupts service or reboots the device.
The record
- CVE
- CVE-2026-34124
- Published
- Apr 2, 2026
- Updated
- Apr 2, 2026
- Vendor
- TP-Link Systems Inc.
- Product
- Tapo C520WS
- Classifications
- CWE-120, 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