VYPR
← All advisories
Medium severityNVD Advisory· Published Jun 6, 2026

CVE-2026-6239

CVE-2026-6239

Description

A stack-based buffer overflow in the ONVIF CreateUsers service of Tapo C520WS v2 allows authenticated attackers to cause a denial-of-service.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A stack-based buffer overflow in the ONVIF CreateUsers service of Tapo C520WS v2 allows authenticated attackers to cause a denial-of-service.

Vulnerability

A stack-based buffer overflow vulnerability exists in the ONVIF CreateUsers service of the Tapo C520WS v2. The device fails to properly validate the number of XML user nodes during request processing. This affects Tapo C520WS v2.

Exploitation

An authenticated attacker can send a specially crafted ONVIF request containing an excessive number of user entries to the CreateUsers service. This triggers memory corruption, leading to a denial-of-service condition.

Impact

Successful exploitation may cause the ONVIF management service to terminate unexpectedly, resulting in a denial-of-service (DoS) condition. This disrupts device configuration and management functions.

Mitigation

TP-Link has released firmware updates to address this vulnerability. Users should update their devices to the latest firmware version. Specific version information and release dates are not detailed in the provided references, but the advisory lists this CVE as resolved [3]. References [1] and [2] provide access to firmware download pages for the Tapo C520WS model.

References
  1. Download for Tapo C520WS | TP-Link
  2. Download for Tapo C520WS | TP-Link
  3. Security Advisory: Multiple Vulnerabilities on TP-Link Tapo C520WS (CVE-2026-6239, CVE-2026-6240, CVE-2026-6241, CVE-2026-6242, CVE-2026-34123)

AI Insight generated on Jun 6, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

3

News mentions

1