CVE-2026-102692: critical vulnerability in RIOT-OS RIOT
RIOT: Potential integer overflow in nanocoap Block2 handling leading to out-of-bounds memory access
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
28Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 9.1epss 0.4%
RIOT is an open-source microcontroller operating system designed for Internet of Things devices and other embedded systems. Prior to 2026.07, nanocoap accepts oversized CoAP Block2 option values without enforcing the 20-bit maximum block number, allowing block offset multiplication to overflow on 32-bit targets. The affected master baseline is commit aeeae69e; the verified fix is later on master and remains unreleased. The oversized value passes from coap_get_blockopt() to coap_block_slicer_init(). A remote CoAP client can send a malformed Block2 option that produces an invalid slice range and can cause out-of-bounds memory access, denial of service, or memory corruption. This vulnerability is fixed in 2026.07.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
Affected products
RIOT-OS · RIOTRelated CVEs — RIOT-OS RIOT
In the same product, most dangerous first.
CVE-2024-32017CRITICALBuffer overflows in RIOTEPSS 1.6%CVE-2024-32018HIGHIneffective size check due to assert() and buffer overflow in RIOTEPSS 1.5%CVE-2023-33975CRITICALRIOT-OS vulnerable to Out of Bounds Write in _rbuf_addEPSS 1.5%CVE-2024-31225HIGHLack of size check and buffer overflow in RIOTEPSS 1.3%CVE-2023-24818HIGHRIOT-OS vulnerable to null pointer dereference during fragment forwardingEPSS 1.2%CVE-2023-24823CRITICALRIOT-OS vulnerable to Packet Type Confusion during IPHC sendEPSS 1.0%