# CVE-2025-14553: Password Hash Leak Could Lead to Unauthorized Access on Tapo App via Local Network

> Attackers on the local network can extract password hashes from the Tapo app to brute force credentials and gain unauthorized access to cameras.

- **Severity:** High 7.0 (`CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/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:** 16 Dec 2025
- **Updated:** 9 Jan 2026
- **Also known as:** GHSA-9v6p-xq76-q833

## What is CVE-2025-14553?

CVE-2025-14553 is a high-severity vulnerability in TP-Link Tapo App, published on 16 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Exposure of password hashes through an unauthenticated API response in TP-Link Tapo app on iOS and Android for Tapo cameras, allowing attackers to brute force the password in the local network. Issue can be mitigated through mobile application updates. Device firmware remains unchanged.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2025-14553 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14553 is a high-severity vulnerability in TP-Link Tapo App, published on 16 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-14553 in the wild and no public exploit code.

Affected product: TP-Link Tapo App. 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-14553/ (Markdown: https://insights.sbomify.com/CVE-2025-14553/index.md)
```

## Sources

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

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