CVE-2026-34118
Heap-based Buffer Overflow Vulnerability Leading to Denial-of-Service in multiple TP-Link Tapo Cameras
A heap-based buffer overflow vulnerability was identified in multiple TP-Link Tapo cameras in the HTTP POST body parsing logic due to missing validation of remaining buffer capacity after dynamic allocation, due to insufficient boundary validation when handling externally supplied HTTP input. An attacker on the same network segment could trigger heap memory corruption conditions by sending crafted payloads that cause write operations beyond allocated buffer boundaries. Successful exploitation causes a Denial-of-Service (DoS) condition, causing the device’s process to crash or become unresponsive.
Fixes and workarounds
Fix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: TPLinkFix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: TPLinkFix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: TPLinkFix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: TPLinkFix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: TPLinkFix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: TPLinkFix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: TPLinkFix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: TPLinkFix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: TPLinkAffected products and versions
| Product | Versions | Authority |
|---|---|---|
| Tapo C520WS v2.6 TP-Link Systems Inc. |
≥ 0; < 1.2.4 Build 260326 Rel.24666n (affected, custom)
Other versions: unaffected |
CNA: TPLink |
| Tapo C100 v5 TP Link Systems Inc. |
≥ 0; < 1.5.4 Build 260528 Rel.11462n (affected, custom)
Other versions: unaffected |
CNA: TPLink |
| Tapo C101 v5 TP Link Systems Inc. |
≥ 0; < 1.5.4 Build 260528 Rel.11462n (affected, custom)
Other versions: unaffected |
CNA: TPLink |
| Tapo C210 v3 TP Link Systems Inc. |
≥ 0; < V3.6_1.2.7 Build 260818 (affected, custom)
Other versions: unaffected |
CNA: TPLink |
| Tapo TC70 v3 TP Link Systems Inc. |
≥ 0; < 1.9.2 Build 261009 Rel.61408n (affected, custom)
Other versions: unaffected |
CNA: TPLink |
| Tapo C200 v3 TP Link Systems Inc. |
≥ 0; < 1.9.2 Build 261009 Rel.61408n (affected, custom)
Other versions: unaffected |
CNA: TPLink |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 4.0 / 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 | CNA: TPLink |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://www.tp-link.com/us/support/download/tapo-c520ws/#Firmware-Release-NotesCNA: TPLink · patch
- https://www.tp-link.com/en/support/download/tapo-c520ws/#Firmware-Release-NotesCNA: TPLink · patch
- https://www.tp-link.com/us/support/faq/5047/CNA: TPLink · vendor-advisory
- https://www.tp-link.com/us/support/download/tapo-c100/v5/#Firmware-Release-NotesCNA: TPLink · patch
- https://www.tp-link.com/en/support/download/tapo-c100/v5/#Firmware-Release-NotesCNA: TPLink · patch
- https://www.tp-link.com/us/support/download/tapo-c101/v5/#Firmware-Release-NotesCNA: TPLink · patch
- https://www.tp-link.com/us/support/download/tapo-c210/v3.60/#Firmware-Release-NotesCNA: TPLink · patch
- https://www.tp-link.com/en/support/download/tc70/v3/#Firmware-Release-NotesCNA: TPLink · patch
- https://www.tp-link.com/en/support/download/tapo-c200/v3/#Firmware-Release-NotesCNA: TPLink · patch
- https://www.tp-link.com/us/support/download/tapo-c200/v3/#Firmware-Release-NotesCNA: TPLink · patch
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.