Semtech LR1110/LR1120/LR1121 SPI Interface write-what-where condition
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.76- |
Summary
A vulnerability classified as problematic has been found in Semtech LR1110, LR1120 and LR1121. This affects an unknown function of the component SPI Interface. Performing a manipulation results in write-what-where condition. This vulnerability is known as CVE-2025-14857. The attack may be carried out on the physical device. No exploit is available.
Details
A vulnerability, which was classified as problematic, was found in Semtech LR1110, LR1120 and LR1121 (version now known). This affects some unknown processing of the component SPI Interface. The manipulation with an unknown input leads to a write-what-where condition vulnerability. CWE is classifying the issue as CWE-123. Any condition where the attacker has the ability to write an arbitrary value to an arbitrary location, often as the result of a buffer overflow. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
An improper access control vulnerability exists in Semtech LoRa LR11xxx transceivers running early versions of firmware where the memory write command accessible via the physical SPI interface fails to enforce write protection on the program call stack. An attacker with physical access to the SPI interface can overwrite stack memory to hijack program control flow and achieve limited arbitrary code execution. However, the impact is limited to the active attack session: the device's secure boot mechanism prevents persistent firmware modification, the crypto engine isolates cryptographic keys from direct firmware access, and all modifications are lost upon device reboot or loss of physical access.
The weakness was published by Egor as psa-2026-001. It is possible to read the advisory at semtech.com. This vulnerability is uniquely identified as CVE-2025-14857 since 12/18/2025. The exploitability is told to be easy. Attacking locally is a requirement. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Write-what-where conditionCWE: CWE-123 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Yes
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
12/18/2025 CVE reserved04/07/2026 Advisory disclosed
04/07/2026 VulDB entry created
04/07/2026 VulDB entry last update
Sources
Advisory: psa-2026-001Researcher: Egor
Status: Confirmed
CVE: CVE-2025-14857 (🔒)
GCVE (CVE): GCVE-0-2025-14857
GCVE (VulDB): GCVE-100-355935
Entry
Created: 04/07/2026 23:28Changes: 04/07/2026 23:28 (69)
Complete: 🔍
Cache ID: 216:45D:103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.