Quick answers
- Is CVE-2026-34123 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-34123 being exploited in the wild.
- How severe is CVE-2026-34123?
- Informational severity, with a CVSS score of 7, published 6 June 2026.
- Which products and versions are affected?
- TP-Link Tapo C520WS v2.
- Is there a fix for CVE-2026-34123?
- 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-34123 attacked?
- It is attacked from the adjacent network, in a network appliance.
- Am I affected by CVE-2026-34123?
- Check whether you run TP-Link Tapo C520WS 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 logic flaw exists in the API authorization mechanism of the TP-Link Tapo C520WS v2. The vulnerability stems from how the device handles 'method mapping' during API requests, which can be leveraged to bypass whitelist restrictions. An authenticated attacker with a restricted account (such as a hub user) can craft requests that mask unauthorized sensitive operations as legitimate, permitted ones. Successful exploitation allows for unauthorized configuration changes, device resets, or denial-of-service conditions. The vendor has released firmware updates to address this and other vulnerabilities on the product support page.
Affected products
- TP-Link Tapo C520WS v2
Timeline
- 2026-06-05: disclosed
- 2026-06-06: advisory