PatchSiren cyber security CVE debrief
CVE-2025-14859 Semtech CVE debrief
The Semtech LR11xx LoRa transceivers implement secure boot functionality using digital signatures to authenticate firmware. However, the implementation uses a non-standard cryptographic hashing algorithm that is vulnerable to second preimage attacks. An attacker with physical access to the device can exploit this weakness to generate a malicious firmware image with a hash collision, bypassing the secure boot verification mechanism and installing arbitrary unauthorized firmware on the device.
- Vendor
- Semtech
- Product
- LR1110
- CVSS
- HIGH 7
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-04-07
- Original CVE updated
- 2026-07-24
- Advisory published
- 2026-04-07
- Advisory updated
- 2026-07-24
Who should care
Organizations using Semtech LR11xx LoRa transceivers in their IoT devices should prioritize patching this vulnerability to prevent potential attacks. The vulnerability's high CVSS score of 7 indicates a significant risk to device security.
Technical summary
The Semtech LR11xx LoRa transceivers use a non-standard cryptographic hashing algorithm for secure boot, which is vulnerable to second preimage attacks. This allows an attacker with physical access to create a malicious firmware image with a hash collision, bypassing secure boot verification and enabling the installation of unauthorized firmware. Affected product deployments should be identified and prioritized for patching, considering the high CVSS score of 7 and potential impact on device security. The vulnerability's exploitation requires physical access to the device, but successful attacks could lead to unauthorized firmware installations, emphasizing the need for prompt patching and monitoring of suspicious firmware updates.
Defensive priority
High priority should be given to patching affected devices, as the vulnerability allows for the installation of arbitrary firmware. Organizations should also consider implementing compensating controls, such as monitoring for suspicious firmware updates and ensuring physical security of devices.
Recommended defensive actions
- Apply patches or updates provided by the vendor to fix the vulnerable hashing algorithm
- Implement monitoring for suspicious firmware updates and ensure physical security of devices
- Consider using alternative secure boot mechanisms that utilize standard cryptographic hashing algorithms
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE record and NVD detail provide information on the vulnerability, but further analysis is needed to fully understand the impact and potential mitigations. The Semtech security bulletin (SEM-PSA-2026-001) likely contains additional details on patching and mitigation strategies.
Sources and references
Verified primary and authoritative sources
-
CVE-2025-14859 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2025-14859
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2025-14859 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2025-14859
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://www.semtech.com/company/security/security-bulletins/sem-psa-2026-001
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.