Medium Memory corruption

CVE-2026-6232 — Out-of-bounds write in LR11xx Transceiver

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.

Published Oct 12, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: Semtech

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.2% (30-day exploitation probability)+1
Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.17%

ahead of 6% of scored CVEs · Oct 14, 2026

Affects

Semtech

LR1110 Modem-e and 4 more

CVSS base

5.2

Medium · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Semtech LR1110 Modem-e, Semtech LR1110 Transceiver, Semtech LR1120 Transceiver…).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Semtech	LR1110 Modem-e	< 2.1.1	Vulnerable	CVE Program (cve.org) e CISA ADP
Semtech	LR1110 Transceiver	< 0x0403	Vulnerable	CVE Program (cve.org) e CISA ADP
Semtech	LR1120 Transceiver	< 0x0203	Vulnerable	CVE Program (cve.org) e CISA ADP
Semtech	LR1121 Modem-e	< 2.1.1	Vulnerable	CVE Program (cve.org) e CISA ADP
Semtech	LR1121 Transceiver	< 0x0105	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Physical

Attack complexity

Low

Attack requirements

None

Privileges required

None

User interaction

None

Scope

Confidentiality (vulnerable system)

None

Integrity (vulnerable system)

High

Availability (vulnerable system)

High

Confidentiality (subsequent)

None

Integrity (subsequent)

None

Availability (subsequent)

None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
5.2	CVSS 4.0	Medium	—	—	security@sierrawireless.com via NIST National Vulnerability Database
5.2	CVSS 4.0	Medium	—	—	Semtech via CVE Program (cve.org) e CISA ADP

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

(score shown at the top: security@sierrawireless.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-787 · Out-of-bounds Write

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.17%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.

endpoint telemetry (EDR)crash dumps

Timeline

What happened to this CVE, newest first.

2026
Affected products added · semtech/lr1110 transceiver, semtech/lr1110 modem-e, semtech/lr1120 transceiver, semtech/lr1121 transceiver, semtech/lr11
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
CVSS changed · 5.2
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Received
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
CVE published
Oct 12, 2026 · Semtech

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

1 on the record

www.semtech.com/company/security/security-bulletins/sem-psa-2026-002-lr11xx-security-
NIST National Vulnerability Database

Elsewhere on this site

Semtech
every CVE for this vendor

Memory corruption
same class

CWE-787
other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No fixed version, patch or mitigation documented.
No CISA SSVC assessment.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-6232 is "Out-of-bounds write in LR11xx Transceiver", rated Medium. It affects LR1110 Modem-e (Semtech); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.2 describes technical severity. EPSS 0.17% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.