Unauthorized firmware installation via collision-prone boot hash
Published Apr 7, 2026 · Updated Apr 7, 2026
Secure-boot bypass in Semtech LR1110, LR1120, and LR1121 firmware allows physically proximate attackers to install unauthorized firmware. The bootloader authenticates firmware with a non-standard hash that permits a second-preimage collision to pass digital-signature verification. Physical device access is required; a forged image can replace trusted firmware with attacker-controlled code.
Summary
What happened
Secure-boot bypass in Semtech LR1110, LR1120, and LR1121 firmware allows physically proximate attackers to install unauthorized firmware. The bootloader authenticates firmware with a non-standard hash that permits a second-preimage collision to pass digital-signature verification. Physical device access is required; a forged image can replace trusted firmware with attacker-controlled code.
The record
- CVE
- CVE-2025-14859
- Published
- Apr 7, 2026
- Updated
- Apr 7, 2026
- Vendor
- Semtech
- Product
- LR1110
- Classifications
- CWE-327, CAPEC-68, T1542.001
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 7, 2026CVE publishedPublication date reported by the CVE source.
- Apr 7, 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 <BL2 FW 0x1001
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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