Skip to main content

Tapo C100/C101 CVE-2026-75619

| EUVDEUVD-2026-62634 MEDIUM
Heap-based Buffer Overflow (CWE-122)
2026-08-19 TPLink GHSA-fg6p-fqhj-j3f8
6.9
CVSS 4.0 · Vendor: TPLink
View

Attack ChainAIDerived

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

  1. Access
    Gain local network access
  2. Delivery
    Authenticate to camera with valid credentials
  3. Exploit
    Connect to RTSP streaming service
  4. Execution
    Send crafted frame with oversized length value
  5. Persist
    Trigger out-of-bounds heap write
  6. Impact
    RTSP service crash and device reboot (temporary DoS)

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Heap 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 (1) be present on the same local network segment as the target camera (adjacent network, AV:A - internet-based remote exploitation is not possible), and (2) hold valid authentication credentials for the camera (PR:L - unauthenticated exploitation is not possible per the CVSS vector). The target device must be a Tapo C100 or C101 on V5 hardware specifically; other hardware revisions are not confirmed affected. The vulnerability is in the RTSP service, meaning that service must be active and reachable - this is typically enabled by default for live-view streaming. The impact is strictly limited to availability: a successful exploit crashes the RTSP service and triggers a device reboot, providing only a temporary denial-of-service with no path to code execution, data exfiltration, or persistent access.

Impact

The CVSS 4.0 vector (AV:A/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N) scores 6.9 and accurately characterizes this as a medium-severity, network-adjacent, authenticated availability issue. Two factors meaningfully reduce real-world risk: the attacker must already hold valid credentials to the camera (PR:L), and must be on the same local network segment (AV:A), ruling out remote internet-based exploitation. The impact ceiling is a temporary service interruption - the camera reboots and resumes normal operation, limiting business impact to brief camera downtime. No EPSS data was provided and this CVE is not listed in the CISA KEV catalog, consistent with the low exploitation priority signal. No public exploit code has been identified. For home and SMB deployments, the primary realistic threat is a rogue insider or a compromised local network device pivoting to disrupt camera coverage. The absence of confidentiality or integrity impact (VC:N/VI:N) means camera footage cannot be accessed or altered through this vulnerability alone.

Exploit ScenarioDerived

An attacker who has obtained valid credentials for a Tapo C100 or C101 V5 camera - through credential stuffing, default password reuse, or prior network compromise - connects to the camera's RTSP service from the local network and sends a crafted RTSP frame with an oversized length field. The oversized value triggers an out-of-bounds heap write in the RTSP service, causing it to crash and forcing the camera to reboot, eliminating camera coverage for the duration of the reboot cycle. No public exploit code has been identified, meaning a potential attacker would need to develop their own proof-of-concept against the RTSP parser.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 19, 2026

Heap-based buffer overflow in the RTSP service of TP-Link Tapo C100 and C101 V5 IP cameras allows an authenticated attacker on the same local network segment to crash the RTSP service and force a device reboot by sending specially crafted frames with oversized length values. Impact is limited to temporary denial-of-service; no confidentiality or integrity compromise is achievable. No public exploit code has been identified at time of analysis, and TP-Link has released firmware patches for affected devices.

RemediationAI

The primary fix is to update affected Tapo C100 V5 and C101 V5 cameras to the patched firmware version published by TP-Link. Exact patched firmware version numbers should be confirmed via the official TP-Link firmware release notes at https://www.tp-link.com/us/support/download/tapo-c100/#Firmware-Release-Notes and https://www.tp-link.com/us/support/download/tapo-c101/#Firmware-Release-Notes, and the accompanying security advisory at https://www.tp-link.com/us/support/faq/5251/. Patch availability is confirmed per vendor advisory but the specific patched firmware version number was not independently verified from the provided data. As an interim compensating control, restrict camera management and RTSP access to trusted VLANs using firewall or router ACLs to prevent untrusted local network devices from reaching the cameras; note this does not eliminate risk from insider threats or already-compromised network hosts. Rotating camera credentials to strong, unique passwords reduces the authenticated attack surface.

Affected VersionsENISA

Tapo C101 v5 0 <1.5.4 Build 260528 Rel.11462n
Tapo C100 v5 0 <1.5.4 Build 260528 Rel.11462n

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 affected devices are TP-Link Tapo series home IP cameras, specifically hardware version V5 of the C100 and C101 models (CPE: cpe:2.3:a:tp-link_systems_inc.:tapo_c100_v5 and tapo_c101_v5). The vulnerability resides in the RTSP (Real Time Streaming Protocol) service, which is the standard streaming protocol used to deliver live video feeds from the camera. CWE-122 (Heap-based Buffer Overflow) identifies the root cause: the RTSP service fails to validate user-supplied length values in incoming frame data before copying them into a fixed-size heap buffer, allowing writes beyond the allocated buffer boundary. On embedded IoT firmware, such out-of-bounds heap writes most commonly corrupt adjacent heap metadata or function pointers, leading to a crash rather than controllable code execution, which is consistent with the availability-only impact reflected in the CVSS vector.

Know when Tapo C100 V5 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 6.9 MEDIUM
CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
vuln.today AI 5.7 MEDIUM

Adjacent network vector (AV:A) and low-privilege requirement (PR:L) reflect local-network-only, authenticated access; availability-only impact with unchanged scope matches the temporary DoS outcome.

3.1 AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:A/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (TPLink).

CVSS VectorVendor: TPLink

Attack Vector
Adjacent
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
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

DescriptionCVE.org

Tapo C100/C101 V5 contains a heap-based buffer overflow vulnerability in the RTSP service. An authenticated attacker on the local network can send specially crafted RTSP frame data containing oversized length values, resulting in out-of-bounds heap writes.

Successful exploitation can crash the RTSP service and trigger a device reboot, resulting in a temporary denial-of-service condition.

Threat Intelligence Overview

EPSS Score
0.2%
Top 88% exploitable
Prevalence
Medium
popular consumer home IP camera with broad retail distribution
Data Quality
5 sources
Confidence: Medium

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 MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.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

34
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +34
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 heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy