Potential Buffer Overflow in LoRaMac-node
Priority MEDIUM 40CWE-120Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Code execution
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-120 and the CVSS impact.
Summary
In LoRaMac-node before 4.4.4, a reception buffer overflow can happen due to the received buffer size not being checked. This has been fixed in 4.4.4.
Why it matters now
EPSS 0.00919 60th percentileScored 2026-11-07
Fix Fixed LoRaMac-node (LoRa): 4.4.4
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| LoRa | LoRaMac-node | before 4.4.4 | 4.4.4 | Patch available | CNA |
- LoRaMac-node VendorLoRa Affected before 4.4.4 Fixed in 4.4.4 Patch available CNA
Remediation
- Fix · CNA LoRaMac-node (LoRa) Fixed in 4.4.4
Timeline
- 2026-10-02 Threatist record created from CVE-2020-11068
References
More Semtech Loramac-node vulnerabilities
- TI-2022-18650 Buffer Overflow in `ProcessRadioRxDone` in LoRaMac-node CVSS 3.1CRITICAL 9.8
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences