Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain authenticated ONVIF access on LAN
-
ExploitCraft SOAP request with excess preset elements
-
ExecutionOverflow fixed-size stack array in PTZ handler
-
ImpactCrash ONVIF service (denial of service)
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 | Exploitation requires the attacker to be an authenticated ONVIF client (PR:H) with network reachability to the camera's ONVIF PTZ SOAP service on the adjacent/local network (AV:A), and the ONVIF/PTZ interface must be enabled and accessible. The specific trigger is submitting an excessive number of preset-related elements to the PTZ SOAP handlers, overflowing fixed-size stack arrays. Limiting factors: valid ONVIF credentials are mandatory (no unauthenticated path), the camera is not exposed to the internet by default so an adjacent-network foothold is needed, and the realistic outcome is limited to a recoverable service crash/DoS rather than code execution or data exposure. |
| Impact | This is a genuine but low-to-moderate priority issue whose signals are internally consistent rather than conflicting. The CVSS 4.0 vector (AV:A/AC:L/AT:N/PR:H/UI:N, VA:H with VC:N/VI:N) describes an adjacent-network, low-complexity attack that requires HIGH privileges (PR:H - an already-authenticated ONVIF client) and yields only an availability impact (denial of service), which aligns precisely with the description of a stack out-of-bounds write that crashes the ONVIF PTZ service. The 6.8 (Medium) score is driven entirely by availability loss; there is no confidentiality or integrity impact and no code-execution claim despite CWE-121 (stack-based buffer overflow) - the vendor characterizes the outcome strictly as a crash/DoS, not RCE. No EPSS score, KEV listing, or public POC is present in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation; absence of these is expected for a newly disclosed consumer-device DoS. Two caveats for defenders: (1) PR:H plus AV:A means the attacker must already be an authenticated ONVIF user on the local/adjacent network, sharply limiting real-world risk to insiders or already-compromised LAN footholds; (2) a stack out-of-bounds write (CWE-121) can sometimes be escalated beyond a crash, but the vendor explicitly limits impact to DoS, so any RCE potential is unverified and should not be assumed. |
| Exploit ScenarioDerived | An attacker with valid ONVIF credentials on the same local network as the Tapo C500 camera connects to the ONVIF PTZ SOAP endpoint and sends a crafted request containing an excessive number of preset-related elements. The oversized input overflows a fixed-size stack array in the PTZ handler, corrupting the stack and crashing the ONVIF service, disrupting camera management and PTZ control. No public exploit code is identified at time of analysis; exploitation requires prior authentication and adjacent-network access. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 06, 2026
TP-Link Tapo C500 v2.0 cameras with the ONVIF PTZ interface enabled are vulnerable to an out-of-bounds stack write (CWE-121) that can be triggered by an authenticated ONVIF client sending an excessive number of preset-related elements to the PTZ SOAP handlers, resulting in a service crash and denial-of-service. Exploitation requires valid ONVIF credentials and adjacency to the camera's network (CVSS 4.0: 6.8, AV:A/PR:H), and while the attacker cannot execute code or access data, repeated crashes can disrupt camera management and PTZ functionality until the service restarts. TP-Link has released a firmware patch, and no public exploit code has been identified at time of analysis.
RemediationAI
Apply the latest firmware update from TP-Link's support page for the Tapo C500 (https://www.tp-link.com/us/support/download/tapo-c500/#Firmware-Release-Notes) as the vendor has released a patch. If immediate patching is not possible, mitigate by restricting network access to the camera's ONVIF/PTZ service to trusted hosts or VLANs, disabling the ONVIF PTZ interface if not required (which removes the attack surface but disables pan-tilt-zoom automation), and ensuring that ONVIF credentials are strong and unique to limit authenticated exploitation. Monitor for service crashes that may indicate attempted exploitation. Note that the camera is not exposed to the internet by default, so keeping it behind NAT and a firewall reduces risk. See the vendor advisory at https://www.tp-link.com/us/support/faq/5327/ for further details.
Affected VersionsENISA
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 resides in the ONVIF PTZ SOAP handlers of the TP-Link Tapo C500 v2.0 firmware. ONVIF (Open Network Video Interface Forum) is a standard protocol used for IP camera management, and the PTZ (pan-tilt-zoom) service defines SOAP operations such as setting or retrieving presets. The affected handlers use fixed-size stack arrays to store preset-related elements without proper bounds checking. When an authenticated client submits an excessive number of these elements, the code writes past the end of the stack buffer, corrupting adjacent stack memory. This is a classic CWE-121 stack-based buffer overflow, but in this case the corruption leads to a crash of the affected service rather than controlled code execution, as indicated by the CVSS impact metrics (no confidentiality or integrity impact, only availability). The CPE cpe:2.3:a:tp-link_systems_inc.:tapo_c500_v2.0:*:*:*:*:*:*:*:* confirms the specific hardware revision affected.
Know when Tapo C500 V2 0 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
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
Adjacent ONVIF access (AV:A) with low complexity; requires an authenticated high-privilege ONVIF client (PR:H); impact is availability-only (A:H), no confidentiality or integrity effect.
Primary rating from Vendor (TPLink).
CVSS VectorVendor: TPLink
DescriptionCVE.org
TP-Link Tapo C500 v2.0 contains an out-of-bounds stack write vulnerability in its ONVIF PTZ SOAP handlers. An authenticated ONVIF client can submit an excessive number of preset-related elements, causing writes beyond the bounds of fixed-size stack arrays and resulting in a crash of the affected service.
Successful exploitation may allow an authenticated attacker to cause the affected service to crash, resulting in a denial-of-service condition. Repeated exploitation may repeatedly disrupt camera management and PTZ-related functionality until the service recovers or restarts.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
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.
EUVD-2026-93839
GHSA-879v-46j6-mx37
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB