Raw vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:U/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:X/V:X/RE:X/U:XCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2025-66647 is a low-severity Classic Buffer Overflow (CWE-120) vulnerability in Riot-Os Riot. Its CVSS base score is 1.7 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Server (T1584.004); ranked in the top 38% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-66647 is a buffer overflow vulnerability (CWE-120) in the IPv6 fragmentation reassembly implementation of RIOT OS version 2025.07, an open-source operating system for Internet of Things (IoT) and embedded devices. The issue resides in the `gnrc_ipv6_ext_frag` module, where copying the contents of the first fragment (with offset=0) into the reassembly buffer lacks a size check. An attacker can force the creation of a small reassembly buffer by sending a shorter initial fragment (also offset=0), enabling subsequent overflow that corrupts adjacent packet buffers.
Any remote attacker with the ability to send arbitrary IPv6 packets to a victim device—including the `gnrc_ipv6_ext_frag` module—can exploit this vulnerability. By manipulating fragment sizes, the attacker triggers buffer overflow, leading to memory corruption of other packet buffers. This can potentially result in further memory corruption or remote code execution, as indicated by the CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
RIOT OS version 2025.10 addresses the vulnerability with a fix, as detailed in the release notes. The affected code lines are documented in the RIOT GitHub repository at lines 411, 481, 532, and 544 of `sys/net/gnrc/network_layer/ipv6/ext/frag/gnrc_ipv6_ext_frag.c`. Security practitioners should ensure devices upgrade to 2025.10 or later and verify if the module is enabled in their builds.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-203946
Vulnerability Data
RIOT is an open-source microcontroller operating system, designed to match the requirements of Internet of Things (IoT) devices and other embedded devices. A vulnerability was discovered in the IPv6 fragmentation reassembly implementation of RIOT OS v2025.07. When copying the contents…
more
of the first fragment (offset=0) into the reassembly buffer, no size check is performed. It is possible to force the creation of a small reassembly buffer by first sending a shorter fragment (also with offset=0). Overflowing the reassembly buffer corrupts the state of other packet buffers which an attacker might be able to used to achieve further memory corruption (potentially resulting in remote code execution). To trigger the vulnerability, the `gnrc_ipv6_ext_frag` module must be included and the attacker must be able to send arbitrary IPv6 packets to the victim. Version 2025.10 fixes the issue.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.2.1
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and analysis can find missing size checks before deployment.
Input validation directly enforces size checks before buffer copies.
Engineering principles require bounds checking and safe buffer handling in design.
Memory protection limits the impact of an overflow once it occurs.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure development practices directly enforce bounds checking and input validation that prevent classic buffer overflows.
Vulnerability identification processes such as code review or scanning detect classic buffer overflows before exploitation.
Routine patching replaces vulnerable code containing unchecked buffer copies with corrected versions.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development and acceptance can detect buffer overflows through fuzzing and static analysis, though it does not prevent them at the source.
Secure coding directly requires bounds-checked memory operations, addressing the root cause of CWE-120.