Skip to main content

Tapo C520WS CVE-2026-6239

| EUVDEUVD-2026-34934 MEDIUM
Stack-based Buffer Overflow (CWE-121)
2026-06-05 TPLink GHSA-cpjh-84vm-rvxf
6.8
CVSS 4.0 · Vendor: TPLink
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Obtain admin credentials via reuse or phishing
  2. Delivery
    Gain access to device LAN segment
  3. Exploit
    Authenticate to ONVIF service with admin account
  4. Install
    Craft SOAP CreateUsers request with excessive XML user nodes
  5. C2
    Send request to ONVIF endpoint
  6. Execute
    Stack buffer overflow triggers service crash
  7. Impact
    ONVIF management DoS condition

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Stack buffer bounds checking
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Three concrete prerequisites must all be satisfied: (1) Adjacent network access - the attacker must be on the same LAN or network segment as the camera (AV:A); internet-based exploitation is not possible without a prior foothold on the local network. (2) High-privilege authentication - the CVSS vector specifies PR:H, meaning the attacker must authenticate to the camera with administrator-level credentials before issuing the ONVIF CreateUsers request; unauthenticated exploitation is not possible. (3) ONVIF service enabled and reachable - the ONVIF management service must be running and accessible on the device, which is standard for this camera model but can be disabled. Limiting factors that reduce realistic risk: the adjacent-only vector eliminates all internet-sourced attacks; the admin credential requirement means an attacker without prior access to camera management cannot weaponize this vulnerability; and the impact is confined to a DoS of the ONVIF service only - no code execution, data exfiltration, or persistent device compromise has been described.

Impact

The CVSS 4.0 score of 6.8 reflects a meaningful but constrained risk profile. The vector AV:A/AC:L/AT:N/PR:H/UI:N breaks down as follows: attack vector is adjacent (LAN segment only - not internet-reachable without prior foothold), complexity is low, and no additional attack requirements exist, but high privileges (PR:H) are mandatory, meaning the attacker must already hold administrator-level credentials on the camera. The impact is limited entirely to availability (VA:H) with zero confidentiality or integrity impact (VC:N/VI:N). No EPSS score was provided in available intelligence, so exploitation probability cannot be quantified. The absence of a KEV listing and no identified public POC further suggests this is not currently being exploited at scale. Real-world risk is low-to-moderate: the combination of adjacent-only access and required admin credentials substantially narrows the realistic attacker population to insiders, compromised LAN actors, or those who have separately acquired admin credentials. The primary operational risk is service disruption to ONVIF-dependent NVR/VMS integrations rather than data breach or device takeover.

Exploit ScenarioDerived

An attacker who has obtained administrator-level credentials to the Tapo C520WS v2 - whether through credential reuse, phishing, or a prior network compromise - connects from the same LAN segment and sends a crafted ONVIF CreateUsers SOAP request containing hundreds of XML user node entries. The camera's ONVIF service processes the malformed request without validating the node count, overflows a fixed-size stack buffer, and the process crashes, taking down ONVIF management functions until the device is rebooted or the service restarts. No public exploit code has been identified at time of analysis.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 06, 2026

Stack-based buffer overflow in the ONVIF CreateUsers service of the TP-Link Tapo C520WS v2 IP camera allows an authenticated, adjacent-network attacker to crash the ONVIF management process by sending a crafted request with an excessive number of XML user nodes. Exploitation results in a denial-of-service condition that disrupts ONVIF-based device configuration and management until the service recovers or the device is rebooted. No public exploit code or CISA KEV listing has been identified at time of analysis; the vendor (TP-Link) has released a firmware patch.

RemediationAI

Apply the latest Tapo C520WS v2 firmware update from the TP-Link official download page (https://www.tp-link.com/us/support/download/tapo-c520ws/#Firmware-Release-Notes or https://www.tp-link.com/en/support/download/tapo-c520ws/#Firmware-Release-Notes) and review the vendor security advisory at https://www.tp-link.com/us/support/faq/5120/ for exact patched version details; the specific fixed firmware build number was not present in available intelligence and must be confirmed against the release notes before deployment. As a compensating control prior to patching, isolate the camera on a dedicated IoT VLAN with firewall rules preventing cross-segment ONVIF access, which eliminates the adjacent-network exposure (AV:A) and fully mitigates remote exploitation at the cost of potentially disrupting cross-VLAN NVR/VMS integrations. If ONVIF functionality is not required for your deployment, disabling the ONVIF service entirely removes the attack surface with no impact on basic camera operation but will break third-party ONVIF-compatible management tools. Additionally, audit and minimize the number of accounts with high-privilege access to the device, as PR:H is a hard prerequisite for exploitation.

Affected VersionsENISA

Tapo C520WS v2 0 <1.2.6 Build 260528

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The TP-Link Tapo C520WS v2 is a consumer-grade outdoor IP camera that implements the ONVIF (Open Network Video Interface Forum) protocol for standardized management interoperability, including the CreateUsers service for provisioning camera accounts via XML-formatted SOAP requests. CWE-121 (Stack-Based Buffer Overflow) identifies the root cause class: the firmware allocates a fixed-size stack buffer to hold parsed XML user node data from the ONVIF CreateUsers request body, but fails to bound-check the number of user entries supplied. Submitting an excessive node count overflows the stack frame, corrupting return addresses or local state and causing the ONVIF service process to terminate. This pattern - insufficient XML input validation in embedded network-facing services - is a recurring weakness in IoT/camera firmware, typically arising from constrained development environments without stack canaries or bounds-checking libraries. The affected CPE is cpe:2.3:a:tp-link_systems_inc.:tapo_c520ws_v2:*:*:*:*:*:*:*:*.

Know when Tapo C520Ws V2 gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (TPLink) PRIMARY 6.8 MEDIUM
CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (TPLink) · only source for this CVE.

CVSS VectorVendor: TPLink

Attack Vector
Adjacent
Attack Complexity
Low
Attack Requirements
None
Privileges Required
High
User Interaction
None
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
None
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

1
CVSS changed
Jun 06, 2026 - 00:22 NVD
6.8 (MEDIUM)

DescriptionCVE.org

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.

Threat Intelligence Overview

EPSS Score
0.0%
Top 97% exploitable
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Controlled
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

34
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +34
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

A stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy