# CVE-2025-14857: Semtech LR11xx Memory Write Access Control Bypass

> An attacker with physical SPI access can overwrite stack memory to hijack control flow and execute arbitrary code during the session.

- **Severity:** Medium 5.4 (`CVSS:4.0/AV:P/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:N/AU:N/R:A/V:D/RE:M`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Apr 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-xjjj-2993-4g39

## What is CVE-2025-14857?

CVE-2025-14857 is a medium-severity memory corruption vulnerability in Semtech LR1110, published on 7 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-123 (Write-what-where Condition)

## Which versions are affected by CVE-2025-14857?


## How do I fix CVE-2025-14857?

No fix has been published for CVE-2025-14857 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-14857 being exploited?

There is no known exploitation of CVE-2025-14857 in the wild and no public exploit code.

Public exploit code:

- https://github.com/Ermensonx/CVE-2025-14857-MongoBleed (github_poc): https://github.com/Ermensonx/CVE-2025-14857-MongoBleed

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-14857 and fix it if it is affected.

What it is: CVE-2025-14857 is a medium-severity memory corruption vulnerability in Semtech LR1110, published on 7 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-14857 in the wild and no public exploit code.

Affected product: Semtech LR1110. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-14857/ (Markdown: https://insights.sbomify.com/CVE-2025-14857/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-14857
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-14857
- OSV: https://osv.dev/vulnerability/CVE-2025-14857

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-14857/
Summaries are generated and may contain mistakes; the official description above is the record.