# CVE-2025-14299: Improper Content-Length Validation in HTTPS Requests on Tapo C200

> An unauthenticated attacker on the local network can cause a denial of service on the Tapo C200 camera via integer overflow in HTTPS Content-Length validation.

- **Severity:** High 7.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Dec 2025
- **Updated:** 22 Dec 2025
- **Also known as:** GHSA-7cw2-wjj4-46p6

## What is CVE-2025-14299?

CVE-2025-14299 is a high-severity vulnerability in TP-Link Systems Inc. Tapo C200 V3, published on 20 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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).

Weakness: CWE-190 (Integer Overflow or Wraparound), CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2025-14299?

It affects 1 product.


Products: Tp-Link Tapo C200 Firmware.

## How do I fix CVE-2025-14299?

No fix has been published for CVE-2025-14299 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-14299 being exploited?

There is no known exploitation of CVE-2025-14299 in the wild and no public exploit code.

## Other vulnerabilities in TP-Link Systems Inc. Tapo C200 V3

- [CVE-2021-4045](https://insights.sbomify.com/CVE-2021-4045/): TP-LINK Tapo C200 remote code execution vulnerability (critical 9.8)
- [CVE-2025-14300](https://insights.sbomify.com/CVE-2025-14300/): Unauthenticated Access to connectAP API Endpoint on Tapo C100, C200 & C425 (high 8.7)
- [CVE-2025-8065](https://insights.sbomify.com/CVE-2025-8065/): Remote Code Execution via Stack-based Buffer Overflow in ONVIF SOAP Parser in TP-Link Tapo C200 and C520WS (high 8.7)
- [CVE-2026-15316](https://insights.sbomify.com/CVE-2026-15316/): Denial-of-Service via Oversized Encrypted Credential Input in TP-Link Tapo C200 (high 7.1)
- [CVE-2026-12760](https://insights.sbomify.com/CVE-2026-12760/): Denial-of-Service Vulnerability via Malformed IPv4 Fragmentation Handling in TP-Link Tapo C200 (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-14299 and fix it if it is affected.

What it is: CVE-2025-14299 is a high-severity vulnerability in TP-Link Systems Inc. Tapo C200 V3, published on 20 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-14299 in the wild and no public exploit code.

Affected product: TP-Link Systems Inc. Tapo C200 V3. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-14299/ (Markdown: https://insights.sbomify.com/CVE-2025-14299/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-14299
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-14299
- OSV: https://osv.dev/vulnerability/CVE-2025-14299

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-14299/
Summaries are generated and may contain mistakes; the official description above is the record.