# CVE-2025-10991: Root Access via UART

> Attackers with physical access can gain root privileges via UART, compromising the TP-Link Tapo D230S1 smart home device.

- **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:** 30 Sep 2025
- **Updated:** 30 Sep 2025
- **Also known as:** GHSA-w8gv-m6q2-jj9p

## What is CVE-2025-10991?

CVE-2025-10991 is a high-severity authentication bypass vulnerability in TP-Link Systems Inc. Tapo D230S1 V1.20, published on 30 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The attacker may obtain root access by connecting to the UART port and this vulnerability requires the attacker to have the physical access to the device.

This issue affects Tapo D230S1 V1.20: before 1.2.2 Build 20250907.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2025-10991 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10991 is a high-severity authentication bypass vulnerability in TP-Link Systems Inc. Tapo D230S1 V1.20, published on 30 Sep 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-10991 in the wild and no public exploit code.

Affected product: TP-Link Systems Inc. Tapo D230S1 V1.20. 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-10991/ (Markdown: https://insights.sbomify.com/CVE-2025-10991/index.md)
```

## Sources

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

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