# CVE-2026-6232: Out-of-bounds write in LR11xx Transceiver

> An attacker with physical and SPI bus access can trigger an out-of-bounds write in Semtech LR11xx transceiver firmware, potentially leading to code execution or denial of service.

- **Severity:** Medium 5.2 (`CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N/R:U/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:** 12 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-p9mw-jx6h-2wjg

## What is CVE-2026-6232?

CVE-2026-6232 is a medium-severity memory corruption vulnerability in Semtech LR1110 Modem-e, published on 12 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An out-of-bounds write vulnerability in the SPI host command interface of Semtech's LR11xx transceiver firmware where a crafted SPI host command with an oversized length field can cause the firmware to write up to 254 arbitrary bytes past the bounds of an internal, non-persistent memory buffer. Exploitation requires physical access to the device and logical access to the SPI bus.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2026-6232?


## How do I fix CVE-2026-6232?

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

## Is CVE-2026-6232 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6232 and fix it if it is affected.

What it is: CVE-2026-6232 is a medium-severity memory corruption vulnerability in Semtech LR1110 Modem-e, published on 12 Oct 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-2026-6232 in the wild and no public exploit code.

Affected product: Semtech LR1110 Modem-e. 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-2026-6232/ (Markdown: https://insights.sbomify.com/CVE-2026-6232/index.md)
```

## Sources

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

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