# CVE-2025-13453: A potential vulnerability was reported in some ThinkPlus USB drives that could allow a user with physical access to read data stored on the drive.


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 14 Jan 2026
- **Updated:** 25 Feb 2026
- **Also known as:** GHSA-75f9-c6rg-g527

## What is CVE-2025-13453?

CVE-2025-13453 is a medium-severity vulnerability in Lenovo ThinkPlus FU100, published on 14 Jan 2026. 

### Official description

A potential vulnerability was reported in some ThinkPlus USB drives that could allow a user with physical access to read data stored on the drive.

Weakness: CWE-311 (Missing Encryption of Sensitive Data)

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

It affects 4 products.


Products: Lenovo Thinkplus Fu100 Firmware, Lenovo Thinkplus Fu200 Firmware, Lenovo Thinkplus Tsd303 Firmware, Lenovo Thinkplus Tu800 Firmware.

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

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

## Is CVE-2025-13453 being exploited?

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

## Other vulnerabilities in Lenovo ThinkPlus FU100

- [CVE-2025-13455](https://insights.sbomify.com/CVE-2025-13455/): Auth bypass in ThinkPlus FU100 (high 7.3)
- [CVE-2025-13454](https://insights.sbomify.com/CVE-2025-13454/): Information disclosure in ThinkPlus FU100 (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13453 is a medium-severity vulnerability in Lenovo ThinkPlus FU100, published on 14 Jan 2026. 
Exploitation: There is no known exploitation of CVE-2025-13453 in the wild and no public exploit code.

Affected product: Lenovo ThinkPlus FU100. 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-13453/ (Markdown: https://insights.sbomify.com/CVE-2025-13453/index.md)
```

## Sources

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

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