Is CVE-2026-34122 exploited in the wild?

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

How severe is CVE-2026-34122?

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-34122?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-34122 attacked?

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

Am I affected by CVE-2026-34122?

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-34122: TP-Link Tapo C520WS stack overflow in configuration handling

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

A security vulnerability exists in the TP-Link Tapo C520WS outdoor security camera. An attacker on the same local network can send a specially crafted configuration request to the device, causing it to crash or reboot. This results in a denial-of-service, preventing the camera from recording video or providing security monitoring until it is restored.

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

Quick answers

Is CVE-2026-34122 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-34122 being exploited in the wild.
How severe is CVE-2026-34122?: 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-34122?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-34122 attacked?: It is attacked from the adjacent network, in a network appliance.
Am I affected by CVE-2026-34122?: 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 stack-based buffer overflow (CWE-121) exists in the configuration handling component of TP-Link Tapo C520WS v2.6 firmware. The vulnerability is caused by insufficient input validation when processing configuration parameters. An attacker with adjacent network access can exploit this by supplying an excessively long value for a vulnerable parameter, leading to a stack overflow. Successful exploitation results in a service crash or device reboot (Denial of Service). The issue 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

References

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