cve.bz

CVE-2026-34118 tp-link tapo c520ws firmware: Heap-based Buffer Overflow

7.1 highEPSS 0.5%

High (7.1) in tp-link tapo c520ws firmware. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 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

CVSS 3.1

6.5 medium
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 40th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-04-02. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-122 Heap-based Buffer Overflow
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-34118 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-34118?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-34118?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-34118 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-34118

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-34118](https://cve.bz/cve/badge/CVE-2026-34118.svg)](https://cve.bz/cve/CVE-2026-34118)

HTML:

<a href="https://cve.bz/cve/CVE-2026-34118"><img src="https://cve.bz/cve/badge/CVE-2026-34118.svg" alt="CVE-2026-34118"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
TP-Link Systems Inc. Tapo C520WS v2.6before 1.2.4 Build 260326 Rel.24666n
TP Link Systems Inc. Tapo C100 v5before 1.5.4 Build 260528 Rel.11462n
TP Link Systems Inc. Tapo C101 v5before 1.5.4 Build 260528 Rel.11462n
TP Link Systems Inc. Tapo C210 v3before V3.6_1.2.7 Build 260818

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON