Vulnerability · CVE-2025-14299
The HTTPS server on Tapo C200 V3 does not properly validate the Content-Length header, which can lead to an integer overflow.
Published Dec 20, 2025 · catalog updated Dec 22, 2025 · TP-Link Systems Inc. Tapo C200 V3
Last checked Nov 2, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2025-14299. EPSS is 0.24%. Act only if a listed version of TP-Link Systems Inc. Tapo C200 V3 is installed.
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2025-8065 · High
- Severity
- High7.1
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.24%
- Remediation
- Version ranges on file
- Affected products
- vendor TP-Link Systems Inc. Tapo C200 V3 0 <C200(US)_V3_1.4.5 Build 251104
The HTTPS server on Tapo C200 V3 does not properly validate the Content-Length header, which can lead to an integer overflow. An unauthenticated attacker on the same local network segment can send crafted HTTPS requests to trigger excessive memory allocation, causing the device to crash and resulting in denial-of-service (DoS).
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- vendor TP-Link Systems Inc. Tapo C200 V3 0 <C200(US)_V3_1.4.5 Build 2511040 <C200(US)_V3_1.4.5 Build 251104
How to fix CVE-2025-14299
Upgrade
CVE-2025-14299 lists a fix boundary at C200(US)_V3_1.4.5. Compare the installed build with that boundary before you change production.
Version check
Seen in 0 <C200(US)_V3_1.4.5 Build 251104
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2025-14299. EPSS is 0.24%. Act only if a listed version of TP-Link Systems Inc. Tapo C200 V3 is installed.
Which versions are affected?
Compare what you have installed with TP-Link Systems Inc. Tapo C200 V3 0 <C200(US)_V3_1.4.5 Build 251104 0 <C200(US)_V3_1.4.5 Build 251104. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.24%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Dec 20, 2025 · EUVD
Detected
The HTTPS server on Tapo C200 V3 does not properly validate the Content-Length header, which can lead to an integer overflow. An unauthenticated attacker on the same local network segment can send crafted HTTPS requests to trigger excessive memory allocation, causing the device to crash and resulting in denial-of-service (DoS).
Dec 22, 2025 · EUVD
Updated
The HTTPS server on Tapo C200 V3 does not properly validate the Content-Length header, which can lead to an integer overflow. An unauthenticated attacker on the same local network segment can send crafted HTTPS requests to trigger excessive memory allocation, causing the device to crash and resulting in denial-of-service (DoS).
Sources
- CVE.orgVulnerability recordCVE-2025-14299
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2025-14299
30-day exploitation probability 0.24%
first.org - EUVDVulnerability recordEUVD-2025-204620
The HTTPS server on Tapo C200 V3 does not properly validate the Content-Length header, which can lead to an integer overflow. An unauthenticated attacker on the same local network segment can send crafted HTTPS requests to trigger excessive memory allocation, causing the device t
euvd.enisa.europa.eu
References
Freshness
Last verified in this catalog Nov 2, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- FIRST EPSSNov 2, 2026
- CVE.orgNov 2, 2026
- EUVDNov 1, 2026