Menu

Star on GitHub · 3.2k

CVE-2026-6239

A stack‑based buffer overflow vulnerability exists in Tapo C520WS v2 in the ONVIF CreateUsers service, where the device fails to properly validate the number of XML user nodes during request proces…

Published Jun 6, 2026CWE-121EPSS 0.28%

Overview

CVE-2026-6239 is a known-severity vulnerability. It was published on June 6, 2026.

Technical description

A stack‑based

buffer overflow vulnerability exists in Tapo C520WS v2 in the ONVIF CreateUsers service, where

the device fails to properly validate the number of XML user nodes during

request processing. An authenticated attacker can send a specially crafted

ONVIF request containing an excessive number of user entries to trigger memory

corruption.

Successful

exploitation may cause the ONVIF management service to terminate unexpectedly,

resulting in a denial‑of‑service (DoS) condition that disrupts device

configuration and management functions.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-6239?

CVE-2026-6239 is a known-severity vulnerability. It was published on June 6, 2026.

How severe is CVE-2026-6239?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-6239?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-6239?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-6239 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.