CVE-2025-69893: n/a
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.
AI Analysis
Technical Summary
CVE-2025-69893 identifies a side-channel vulnerability in the BIP-39 mnemonic processing of Trezor hardware wallets versions 1.13.0 to 1.14.0. The vulnerability stems from the BIP-39 standard's non-constant time execution and branching patterns during mnemonic word searching, which leak information through side channels. An attacker with physical access during the wallet's initial setup phase can obtain a single side-channel trace. Using profiling-based deep learning side-channel analysis (DL-SCA), the attacker can extract the mnemonic phrase, compromising wallet security. The vendor has released patches to address this vulnerability.
Potential Impact
If exploited, this vulnerability allows an attacker with physical access during the initial setup phase to recover the wallet's mnemonic phrase via side-channel analysis, enabling theft of the wallet's assets. The attack requires physical access and specialized analysis techniques. There are no known exploits in the wild. The vendor has patched the issue, mitigating the risk for updated devices.
Mitigation Recommendations
The vulnerability has been patched by the vendor. Users should update their Trezor hardware wallets to versions later than 1.14.0 to ensure the fix is applied. No additional mitigation is required if the device is updated. For devices that cannot be updated, avoid exposing the device to untrusted physical access during the initial setup phase.
CVE-2025-69893: n/a
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2025-69893 identifies a side-channel vulnerability in the BIP-39 mnemonic processing of Trezor hardware wallets versions 1.13.0 to 1.14.0. The vulnerability stems from the BIP-39 standard's non-constant time execution and branching patterns during mnemonic word searching, which leak information through side channels. An attacker with physical access during the wallet's initial setup phase can obtain a single side-channel trace. Using profiling-based deep learning side-channel analysis (DL-SCA), the attacker can extract the mnemonic phrase, compromising wallet security. The vendor has released patches to address this vulnerability.
Potential Impact
If exploited, this vulnerability allows an attacker with physical access during the initial setup phase to recover the wallet's mnemonic phrase via side-channel analysis, enabling theft of the wallet's assets. The attack requires physical access and specialized analysis techniques. There are no known exploits in the wild. The vendor has patched the issue, mitigating the risk for updated devices.
Mitigation Recommendations
The vulnerability has been patched by the vendor. Users should update their Trezor hardware wallets to versions later than 1.14.0 to ensure the fix is applied. No additional mitigation is required if the device is updated. For devices that cannot be updated, avoid exposing the device to untrusted physical access during the initial setup phase.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- mitre
- Date Reserved
- 2026-01-09T00:00:00.000Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69de56e582d89c981fb19045
Added to database: 4/14/2026, 3:01:57 PM
Last enriched: 4/14/2026, 3:17:10 PM
Last updated: 4/15/2026, 6:02:20 AM
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.