Read the docs
TI-2026-70117 Aliases CVE-2026-107837

Out-of-bounds read in RIOT 6LoWPAN fragment handling

Priority MEDIUM 42CWE-125Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
Low · None · High
Fix status
No fix listed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA.

Summary

RIOT, an operating system for embedded and Internet of Things devices, is affected in version 2026.07 and earlier. Its 6LoWPAN receive path can pass an undersized packet to fragment handling, which reads header fields without checking that the packet holds those bytes (CWE-125). A remote attacker can send a malformed fragment that makes gnrc_sixlowpan_frag_recv() read beyond the packet buffer, possibly disclosing memory and crashing the network stack.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Description from the CNA

RIOT is an open-source microcontroller operating system designed for Internet of Things devices and other embedded systems. In 2026.07 and earlier, _receive() in sys/net/gnrc/network_layer/sixlowpan/gnrc_sixlowpan.c can route an undersized packet into SFF fragment handling after only a minimal payload check. The code then interprets the packet as a sixlowpan_frag_t or larger fragment header without verifying that the packet snip contains the required bytes. A remote attacker can send a malformed 6LoWPAN fragment that causes gnrc_sixlowpan_frag_recv() to read beyond the packet buffer, potentially disclosing memory and crashing the network stack. No fixed repository release is available as of this review.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00378 31st percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
RIOT-OSRIOTup to 2026.07—No fix listedCNA
  • RIOT VendorRIOT-OS Affected up to 2026.07 Fixed in — No fix listed CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:o:riot-os:riot:*:*:*:*:*:*:*:*——RIOT-OS
  • cpe:2.3:o:riot-os:riot:*:*:*:*:*:*:*:* Versions — — ·RIOT-OS

Remediation

The sources list no fixed version for RIOT.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Timeline

  1. 2026-10-10 Threatist record created from CVE-2026-107837
  2. 2026-10-11 Priority changed: MEDIUM → LOW
  3. 2026-10-13 CISA SSVC decision points changed
  4. 2026-10-13 Priority changed: LOW → MEDIUM

References

Other 3

  • TI-2024-21112 Buffer overflows in RIOT CVSS 3.1CRITICAL 9.8
  • TI-2023-16843 RIOT-OS vulnerable to Out of Bounds Write in _rbuf_add CVSS 3.1CRITICAL 9.8
  • TI-2023-10319 RIOT-OS vulnerable to Buffer Overflow during IPHC receive CVSS 3.1CRITICAL 9.8
  • TI-2026-22079 RIOT has an Out-of-Bounds Write in nanoCoAP Handler CVSS 3.1CRITICAL 9.8
  • TI-2023-16842 RIOT-OS vulnerable to Race Condition in SFR Timeout CVSS 3.1HIGH 7.5
  • TI-2023-16841 RIOT-OS vulnerable to NULL pointer dereference during NHC encoding CVSS 3.1HIGH 7.5
See all 45 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences