Is CVE-2026-34124 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-34124 being exploited in the wild.

How severe is CVE-2026-34124?

Medium severity, with a CVSS score of 6.5, published 2 April 2026.

Which products and versions are affected?

TP-Link Tapo C520WS before 1.2.4 Build 260326 Rel.24666n.

Is there a fix for CVE-2026-34124?

A patch was published on 2026-04-02: Fixed in version 1.2.4 Build 260326 Rel.24666n Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-34124 attacked?

It is attacked from the adjacent network, in a network appliance.

Am I affected by CVE-2026-34124?

Check whether you run TP-Link Tapo C520WS or TP-Link Tapo C520ws Firmware at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-34124: TP-Link Tapo C520WS buffer overflow in HTTP path parsing

CVE-2026-34124 · Severity: medium · CVSS 6.5 · Published 2026-04-02

A security vulnerability exists in the TP-Link Tapo C520WS outdoor security camera that could allow an attacker on the same local network to crash the device. By sending a specially crafted web request, an attacker can cause the camera to stop functioning or reboot repeatedly. This disrupts continuous video monitoring and security recording, potentially leaving a property unmonitored.

Technologies: TP-Link Tapo C520WS, TP-Link Tapo C520ws Firmware. Vendors: TP-Link.

Quick answers

Is CVE-2026-34124 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-34124 being exploited in the wild.
How severe is CVE-2026-34124?: Medium severity, with a CVSS score of 6.5, published 2 April 2026.
Which products and versions are affected?: TP-Link Tapo C520WS before 1.2.4 Build 260326 Rel.24666n.
Is there a fix for CVE-2026-34124?: A patch was published on 2026-04-02: Fixed in version 1.2.4 Build 260326 Rel.24666n Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-34124 attacked?: It is attacked from the adjacent network, in a network appliance.
Am I affected by CVE-2026-34124?: Check whether you run TP-Link Tapo C520WS or TP-Link Tapo C520ws Firmware at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A classic buffer overflow (CWE-120) exists in the HTTP request path parsing logic of the TP-Link Tapo C520WS v2.6. While the firmware enforces length checks on raw incoming request paths, it fails to account for potential string expansion during the path normalization process. An unauthenticated attacker on the adjacent network can exploit this by sending a crafted HTTP request that expands beyond allocated buffer limits during processing. This results in memory corruption and a denial-of-service (DoS) condition, typically manifesting as a system crash or device reboot. The vulnerability is addressed in firmware version 1.2.4 Build 260326 Rel.24666n and later.

Affected products

TP-Link Tapo C520WS v2.6 before 1.2.4 Build 260326 Rel.24666n

Timeline

2026-04-02: disclosed
2026-04-02: advisory
2026-04-02: patched: Fixed in version 1.2.4 Build 260326 Rel.24666n

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.