# CVE-2025-1099: Information Disclosure Vulnerability in TP-Link Tapo C500 Wi-Fi Camera

> Attackers with physical access can extract hard-coded RSA keys to decrypt data and impersonate the camera.

- **Severity:** High 7.0 (`CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/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:** 10 Feb 2025
- **Updated:** 14 Feb 2025
- **Also known as:** GHSA-xhcv-4cg2-46v5

## What is CVE-2025-1099?

CVE-2025-1099 is a high-severity vulnerability in TP-Link Tapo C500 V1 Wi-Fi Camera, published on 10 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

This vulnerability exists in Tapo C500 Wi-Fi camera due to hard-coded RSA private key embedded within the device firmware. An attacker with physical access could exploit this vulnerability to obtain cryptographic private keys which can then be used to perform impersonation, data decryption and man in the middle attacks on the targeted device.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

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


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

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

## Is CVE-2025-1099 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-1099 is a high-severity vulnerability in TP-Link Tapo C500 V1 Wi-Fi Camera, published on 10 Feb 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-1099 in the wild and no public exploit code.

Affected product: TP-Link Tapo C500 V1 Wi-Fi Camera. 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-1099/ (Markdown: https://insights.sbomify.com/CVE-2025-1099/index.md)
```

## Sources

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

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