CVE-2026-6232 json
Out-of-bounds write in LR11xx Transceiver
published 30d ago modified 26d ago also EUVD-2026-97726
- cvss
- 5.2
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 6%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Semtech LR1110 Transceiver 0x0403, A1_0303
- Semtech LR1110 Modem-e 2.1.1
- Semtech LR1120 Transceiver 0x0203, A2_0101
- Semtech LR1121 Transceiver 0x0105, A3_0101
- Semtech LR1121 Modem-e 2.1.1
Is CVE-2026-6232 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 27d ago
Exploit prediction
0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 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 |
| CNA | 4.0 | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:U/V:X/RE:M/U:X |
Affected products
- Semtech LR1110 Transceiver
- Semtech LR1110 Modem-e
- Semtech LR1120 Transceiver
- Semtech LR1121 Transceiver
- Semtech LR1121 Modem-e
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
Sources
- CVE List CVE-2026-6232
- NVD CVE-2026-6232
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.