Skip to main content

Tapo C520Ws V2 6 CVE-2026-34122

| EUVDEUVD-2026-18434 HIGH
Stack-based Buffer Overflow (CWE-121)
2026-04-02 TPLink GHSA-hx8v-fm8j-mj2j
7.1
CVSS 4.0 · Vendor: TPLink
View

Attack ChainAIDerived

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

  1. Access
    Connect to adjacent network
  2. Exploit
    Send crafted config parameter
  3. Execution
    Overflow stack buffer
  4. Impact
    Crash device or trigger reboot

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

TP-Link Tapo C520WS v2.6 with vulnerable configuration handling component. Attacker with adjacent network access (AV:A) supplies excessively long value to vulnerable configuration parameter, causing stack overflow and DoS. No authentication or user interaction required.

Impact

Without a CVSS vector or score provided, risk assessment relies on the attack surface characteristics and impact type. The vulnerability results in denial-of-service only, not confidentiality or integrity compromise, limiting its severity impact to availability. The attack vector is assumed to be network-based (typical for IP camera configuration interfaces), but authentication requirements cannot be confirmed from available data. The presence of a vendor-released patch reduces operational risk for patched deployments. However, the criticality depends on whether the vulnerable configuration parameter accepts unauthenticated input and whether widespread deployments remain on v2.6. Organizations using Tapo C520WS cameras in security-critical applications where availability is paramount should prioritize patching, though this is not a critical RCE scenario.

Exploit ScenarioDerived

An attacker on the network sends a configuration request to the Tapo C520WS v2.6 camera with an excessively long parameter value targeting the vulnerable configuration handling component. The oversized input overflows the stack buffer, corrupting memory and causing the camera firmware to crash or reboot. The camera becomes unavailable for recording and live viewing until manually restarted, disrupting security monitoring. No public exploit code availability is confirmed at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.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 – Apr 02, 2026

Stack-based buffer overflow in TP-Link Tapo C520WS v2.6 allows remote attackers to trigger denial-of-service by sending oversized configuration parameters to a vulnerable configuration handling component. Successful exploitation causes device crash or reboot, impacting camera availability. Vendor has released a patch.

RemediationAI

Upgrade TP-Link Tapo C520WS v2.6 firmware to the patched version released by TP-Link. Firmware updates are available from the vendor's official support pages at https://www.tp-link.com/us/support/download/tapo-c520ws/#Firmware-Release-Notes and the corresponding international support page. Detailed patch information and FAQ regarding the vulnerability is available at https://www.tp-link.com/us/support/faq/5047/. Users should download the latest firmware from these official channels and apply the update through the camera's web interface or companion application to restore security.

Affected VersionsENISA

Tapo C520WS v2.6 0 <1.2.4 Build 260326 Rel.24666n

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 vulnerability exists in a configuration handling component of the Tapo C520WS IP camera firmware (v2.6) and stems from insufficient input validation on configuration parameters processed on the stack (CWE-121: Stack-based Buffer Overflow). When an attacker supplies an excessively long value for a vulnerable parameter, the overflow corrupts the stack, leading to uncontrolled program flow termination or device reboot. The affected product is identified by CPE cpe:2.3:a:tp-link_systems_inc.:tapo_c520ws_v2.6:*:*:*:*:*:*:*:*, indicating the Tapo C520WS v2.6 firmware line from TP-Link Systems Inc.

Know when Tapo C520Ws V2 6 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 7.1 HIGH
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/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
None
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

2
Patch released
Apr 02, 2026 - 17:30 nvd
Patch available
CVE Published
Apr 02, 2026 - 17:20 nvd
HIGH 7.1

DescriptionCVE.org

A stack-based buffer overflow vulnerability was identified in TP-Link Tapo C520WS v2.6 within a configuration handling component due to insufficient input validation. An attacker can exploit this vulnerability by supplying an excessively long value for a vulnerable configuration parameter, resulting in a stack overflow.

Successful exploitation results in Denial-of-Service (DoS) condition, leading to a service crash or device reboot, impacting availability.

Threat Intelligence Overview

EPSS Score
0.0%
Top 97% exploitable
Data Quality
6 sources
Confidence: High

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 HIGH
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.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

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
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