Permanent device bricking via unchecked reset handler
Published May 19, 2026 · Updated May 19, 2026
Improper input validation in Ledger Nano X, Flex, and Stax firmware allows physically proximate attackers to permanently brick devices. The MCU bootloader accepts the host-supplied reset_handler address without range, alignment, or signature checks before resuming execution after flashing. Exploitation requires physical access to the firmware-update path; an invalid or non-executable address leaves both external interfaces unresponsive and requires factory-level recovery.
Summary
What happened
Improper input validation in Ledger Nano X, Flex, and Stax firmware allows physically proximate attackers to permanently brick devices. The MCU bootloader accepts the host-supplied reset_handler address without range, alignment, or signature checks before resuming execution after flashing. Exploitation requires physical access to the firmware-update path; an invalid or non-executable address leaves both external interfaces unresponsive and requires factory-level recovery.
The record
- CVE
- CVE-2025-15645
- Published
- May 19, 2026
- Updated
- May 19, 2026
- Vendor
- Ledger
- Product
- Ledger Stax
- Classifications
- CWE-1284, T1495
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 19, 2026CVE publishedPublication date reported by the CVE source.
- May 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.6.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo