Skip to main content

Lr1110 EUVDEUVD-2025-209287

| CVE-2025-14859 HIGH
Use of a Broken or Risky Cryptographic Algorithm (CWE-327)
2026-04-07 SWI
7.0
CVSS 4.0 · Vendor: SWI
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Approved algorithm selection
Impact

Real-world risk is constrained but non-negligible for targeted attacks on high-value IoT deployments. CVSS 7.0 reflects high confidentiality/integrity impact (VC:H/VI:H) but requires physical proximity (AV:P), creating a threat model limited to supply chain tampering, insider threats, or physical device compromise in unattended installations (smart city sensors, industrial IoT). Attack complexity is low (AC:L) with no privilege requirements (PR:N), meaning any attacker with device access can exploit this. The vulnerability is not automatable at scale due to physical access requirements, reducing mass exploitation risk. No CISA KEV listing or public exploit code exists, and SSVC likely categorizes this as 'attended' deployment context with 'efficient' technical impact. However, for critical infrastructure IoT (energy grids, water systems) or devices processing sensitive telemetry, the inability to trust firmware provenance poses significant long-term supply chain risk. Organizations using LR11xx in tamper-evident enclosures or physically secured environments face lower practical risk than those with field-deployed, accessible devices.

Exploit ScenarioDerived

An attacker intercepts LR1120-based asset trackers during shipping or gains temporary physical access to unattended smart agriculture sensors in a field deployment. Using publicly disclosed details of the non-standard hash algorithm, the attacker precomputes hash collisions offline, generating malicious firmware that matches the hash of legitimate signed firmware. They connect to the device's debug/programming interface, flash the malicious firmware, and the secure boot mechanism validates the forged signature, installing backdoored code. The compromised firmware exfiltrates sensor data, manipulates telemetry readings, or provides persistent remote access to the LoRaWAN network, with no runtime indication of compromise since secure boot validation succeeded.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Apr 07, 2026

Cryptographic bypass in Semtech LR11xx LoRa transceiver secure boot allows physically proximate attackers to install arbitrary firmware via hash collision. The implementation uses a non-standard, collision-vulnerable hashing algorithm (CWE-327), enabling second preimage attacks that forge signed firmware images. Affects LR1110, LR1120, and LR1121 transceivers widely deployed in IoT/LoRaWAN devices. CVSS 7.0 requires physical access (AV:P), low complexity, no privileges. No public exploit identified at time of analysis; EPSS data unavailable for this recent CVE.

RemediationAI

Consult Semtech security bulletin SEM-PSA-2026-001 at https://www.semtech.com/company/security/security-bulletins/sem-psa-2026-001 for firmware updates implementing standards-compliant cryptographic hashing (likely SHA-256 or SHA-3). Patch availability and specific fixed firmware versions must be confirmed from the vendor advisory, as silicon-level secure boot fixes may require hardware revision or microcode updates that cannot be field-deployed. If firmware patches are unavailable, implement compensating controls including physical tamper-evident enclosures, restricted device access in secure locations, and runtime integrity monitoring where feasible. For new deployments, evaluate alternative LoRa transceivers with verified secure boot implementations or require vendor attestation of cryptographic algorithm compliance with NIST FIPS 180-4 or equivalent standards. Supply chain security reviews should verify firmware authenticity through independent cryptographic validation before device commissioning.

Affected VersionsENISA

LR1121 0 <BL2 FW 0x2101
LR1110 0 <BL2 FW 0x1001
LR1120 0 <BL2 FW 0x2001

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The LR11xx family (LR1110, LR1120, LR1121) are LoRa transceivers used in IoT sensor nodes, asset trackers, and smart meters requiring long-range wireless connectivity. Secure boot implementations typically use cryptographic signatures (RSA/ECDSA) over standardized hashes (SHA-256/SHA-3) to verify firmware integrity before execution. CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) indicates Semtech implemented a proprietary or deprecated hash function susceptible to second preimage attacks - where an attacker with one valid signed firmware can computationally find a different malicious firmware producing the same hash. Unlike collision attacks (two arbitrary inputs), second preimage attacks directly forge valid signatures for existing legitimate firmware hashes. This fundamentally defeats the secure boot chain-of-trust, as the digital signature verification passes for attacker-controlled code.

Know when Lr1110 gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (SWI) PRIMARY 7.0 HIGH
CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:N/AU:N/R:I/V:C/RE:M

Primary rating from Vendor (SWI) · only source for this CVE.

CVSS VectorVendor: SWI

Attack Vector
Physical
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
Low
Subsequent system: Integrity
Low
Subsequent system: Availability
None

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

Semtech LR11xx LoRa transceivers (LR1110, LR1120, LR1121) contain a cryptographic bypass in secure boot that allows physically proximate attackers to install unauthorized firmware through hash collision attacks. Organizations deploying these transceivers in IoT and LoRaWAN infrastructure face risk of device compromise and potential supply chain integrity violations, particularly in remote or distributed deployment environments where physical access controls are challenging to enforce.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: enforce strict physical access controls at device deployment locations; implement out-of-band firmware integrity verification and monitoring; isolate affected devices on network segments with enhanced monitoring; disable physical debug interfaces where supported; consider temporary replacement with alternative LoRa transceiver models from other vendors for new deployments until patch availability.

Threat Intelligence Overview

EPSS Score
0.0%
Top 97% exploitable
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

35
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +35
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy