intelligence_src_350d40f2cc69277bca
- Source-provided label
- Publisher RSS metadata
- Evidence class
- mentioned in report
- Confidence
- Not reported
- Observed
- Apr 28, 2026 00:00 UTC
- Retrieved
- Oct 13, 2026 08:35 UTC
CVE-2026-34119: TP-Link HTTP POST body heap buffer overflow
An attacker sending a malformed HTTP POST request over LAN to a TP-Link Smart camera device can trigger the vulnerability described here. This report describes a heap buffer overflow, which leads to remote code execution. The vulnerability we are disclosing in this advisory affected a wide range of TP-Link devices, including TAPO Smart Cameras. A TP-Link Security Advisory released in April 2026 contains this vulnerability as CVE-2026-34119. Vulnerability Details another overflow similar to CVE-2026-34118 was present within the main HTTP parser function. This vulnerability can be triggered when more than one receive is required to read the full contents of the body.
Reference details
- Source category
- research-report
- First reported
- Apr 28, 2026 00:00 UTC
- Last reported
- Apr 28, 2026 00:00 UTC
- Catalog updated
- Oct 13, 2026 08:35 UTC
- Record ID
ad6295ecc2014987712595b606b1ffb65cdc683ee233090331fe58d48b8b90b9
Published indicators
Network indicators are visibly defanged. This page does not make them clickable or send them to another service.
No validated file hashes or network indicators are stored for this record.
Source observations
This record contains metadata and attribution only. It does not host, download, unpack, render, or execute malware samples.
Feed collection status
Sources represented on this page. Publication and observation dates describe the content; successful batch dates describe local collection. A recent batch does not certify complete coverage or current provider availability.
1 sources: 0 stale, 0 needing attention, 0 paused, 0 unverified.
Review source update dates and status
- intelligence_src_350d40f2cc69277bcaRecent successful batchLast successful batch: Last attempt:
Stale means older than twice the recorded collection interval, with a minimum of one hour; without an interval, the threshold is 24 hours. Cached content remains available while a feed is stale, paused, or unverified.