Quick answers
- Is CVE-2026-53920 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-53920 being exploited in the wild.
- How severe is CVE-2026-53920?
- Informational severity, published 23 October 2026.
- Which products and versions are affected?
- OpenWrt Odhcpd 17.01.0 to before 25.12.3.
- Is there a fix for CVE-2026-53920?
- Yes: fixed in 25.12.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-53920 attacked?
- It is attacked over the network or from the adjacent network, in a hosted service.
- Am I affected by CVE-2026-53920?
- Check whether you run OpenWrt Odhcpd 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: 25.12.3
Technical details
The DHCPv6 IA option parser reads the IAID field from the option payload without first validating that the option body is at least 12 bytes (as required by RFC8415). A crafted IA_NA or IA_PD option shorter than 12 bytes causes an out-of-bounds read from the adjacent stack buffer, with the leaked bytes reflected in the DHCPv6 reply. This enables an unauthenticated network-adjacent attacker to extract stack canaries and ASLR-relevant contents.
Affected products
- OpenWrt odhcpd 17.01.0 to before 25.12.3
Timeline
- 2026-10-23: disclosed