Quick answers
- Is CVE-2026-49868 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-49868 being exploited in the wild.
- How severe is CVE-2026-49868?
- Critical severity, with a CVSS score of 9.8, published 16 October 2026.
- Which products and versions are affected?
- Riot-Os Riot before 2026.07.
- Is there a fix for CVE-2026-49868?
- Yes: fixed in 2026.07. Until then: Disable MODULE_DHCPV6_CLIENT_IA_PD if DHCPv6 is not required, or restrict network access to trusted DHCPv6 servers only. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-49868 attacked?
- It is attacked over the network, in an operating system.
- Am I affected by CVE-2026-49868?
- Check whether you run Riot-Os Riot at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2026.07
Disable MODULE_DHCPV6_CLIENT_IA_PD if DHCPv6 is not required, or restrict network access to trusted DHCPv6 servers only.
Technical details
The _parse_reply() function in the DHCPv6 client omits validation of minimum option length before passing IA_PD and IA_NA option bodies to sub-option parsers. When MODULE_DHCPV6_CLIENT_IA_PD is enabled, a malicious REPLY with an option length smaller than the required structure causes size_t underflow in _parse_ia_pd_option(), leading to unbounded out-of-bounds heap reads. The vulnerability requires network access to a DHCPv6 server and is fixed by checking option length against sizeof(dhcpv6_opt_ia_pd_t) before parsing.
Affected products
- RIOT-OS RIOT before 2026.07
Timeline
- 2026-10-16: disclosed
- 2026-05-27: patched