# CVE-2025-69893: Information disclosure in n/a

> Physical attackers can recover mnemonic codes via side-channel analysis during setup, leading to asset theft in Trezor hardware wallets.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A: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:** 14 Apr 2026
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-fxwp-fxmc-jh57

## What is CVE-2025-69893?

CVE-2025-69893 is a medium-severity vulnerability in n/a, published on 14 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A side-channel vulnerability exists in the implementation of BIP-39 mnemonic processing, as observed in Trezor One v1.13.0 to v1.14.0, Trezor T v1.13.0 to v1.14.0, and Trezor Safe v1.13.0 to v1.14.0 hardware wallets. This originates from the BIP-39 standard guidelines, which induce non-constant time execution and specific branch patterns for word searching. An attacker with physical access during the initial setup phase can collect a single side-channel trace. By utilizing profiling-based Deep Learning Side-Channel Analysis (DL-SCA), the attacker can recover the mnemonic code and subsequently steal the assets. The issue was patched.

Weakness: CWE-385 (Covert Timing Channel)

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


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

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

## Is CVE-2025-69893 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-69893 is a medium-severity vulnerability in n/a, published on 14 Apr 2026. 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-69893 in the wild and no public exploit code.

Affected product: n/a. 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-69893/ (Markdown: https://insights.sbomify.com/CVE-2025-69893/index.md)
```

## Sources

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

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