odhcpd: Stack buffer overflow in DHCPv6 IA reply serialization (2 independent sites)
No fixed version listed yet.Check the vendor advisory. References ↓
openwrt · odhcpd
The odhcpd DHCPv6 server used by OpenWrt has a stack-based buffer overflow in its IA response handler, where writes can run past a fixed 512-byte buffer (pdbuf). An attacker on the network can trigger it with a single unauthenticated UDP packet, using a DHCPv6 REQUEST carrying enough IA options to nearly exhaust the reply space, with no authentication or user interaction needed; the flaw is fixed in version 25.12.
Official description · NVD
odhcpd is the DHCPv6, DHCPv4, and router-advertisement server used by OpenWrt. Prior to version 25.12, odhcpd's DHCPv6 IA response handler writes past the end of a fixed 512-byte stack buffer (pdbuf) when a single DHCPv6 REQUEST carries enough IA options to nearly exhaust the reply space. Two independent overflow sites exist in the same call chain, both reachable from the network via a single unauthenticated UDP packet. odhcpd runs as root on OpenWrt; embedded targets often lack stack canaries and ASLR, making code execution realistic. This issue has been patched in version 25.12.
- Exploited
- Not confirmed
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
Public exploit code (PoC-in-GitHub) was available 3 months before disclosure.
- Public exploit codePoC-in-GitHub3 mo before
- Disclosedday 0
Affected versions and fixes
as published in the CVE recordopenwrt odhcpd
Affected: < 25.12
What security researchers reported
Not named in any threat report yetAlso mentioned in 7 community threat pulses (AlienVault OTX)
Weaker evidencePulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.
- Known_Cve | Nov 1, 2026 | Part 1/331 Oct 2026
- Known_Cve | Oct 31, 2026 | Part 1/330 Oct 2026
- Known_Cve | Oct 30, 2026 | Part 1/229 Oct 2026
- Known_Cve | Oct 29, 2026 | Part 2/328 Oct 2026
- Known_Cve | Oct 28, 2026 | Part 2/327 Oct 2026
- Known_Cve | Oct 27, 2026 | Part 3/326 Oct 2026
- 1 more on OTX