Live › vulnerability › CVE-2026-49868
Go to dashboardRIOT, an open-source operating system for embedded IoT devices, has a DHCPv6 client that does not check option lengths in REPLY messages before parsing them. A malicious or compromised DHCPv6 server can send a crafted reply that causes out-of-bounds heap reads, crashing the device and possibly exposing or corrupting memory.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
No product ranges from the sources yet.
Check whether the device is built with MODULE_DHCPV6_CLIENT_IA_PD enabled and which RIOT version it runs (unknown if the sources give a command).
Upgrade RIOT to version 2026.07 or later.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
RIOT is an open-source microcontroller operating system designed for Internet of Things devices and other embedded systems. Prior to 2026.07, _parse_reply() in sys/net/application_layer/dhcpv6/client.c omits minimum-length validation before passing IA_PD and IA_NA option bodies to sub-option parsers. A malicious or compromised DHCPv6 server can send a REPLY with an option length smaller than the required structure while MODULE_DHCPV6_CLIENT_IA_PD is enabled, causing _parse_ia_pd_option to read past the option body, size_t underflow, and unbounded out-of-bounds heap reads that can crash the device and may expose or corrupt memory. This issue is fixed in version 2026.07.
This page as .md · .json · in your agent: get_signal("CVE-2026-49868")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.