Critical OpenWrt DHCPv6 Flaw Could Let Unauthenticated Attackers Run Code as Root
A critical stack overflow vulnerability (CVE-2026-53921) in OpenWrt's odhcpd allows unauthenticated remote code execution as root via crafted DHCPv6 REQUEST packets, rated 9.8 on CVSS 3.1 due to lack of stack canaries and ASLR in embedded devices. The flaw involves two independent overflow sites in the DHCPv6 request-processing path where crafted IA options exceed a fixed 512-byte stack buffer without sufficient bounds checking. OpenWrt 24.10.8 and 25.12.5 release includes fixes for this critica
Analysis
TL;DR
- A critical stack overflow vulnerability (CVE-2026-53921) in OpenWrt's odhcpd allows unauthenticated remote code execution as root via crafted DHCPv6 REQUEST packets, rated 9.8 on CVSS 3.1 due to lack of stack canaries and ASLR in embedded devices.
- The flaw involves two independent overflow sites in the DHCPv6 request-processing path where crafted IA options exceed a fixed 512-byte stack buffer without sufficient bounds checking.
- OpenWrt 24.10.8 and 25.12.5 release includes fixes for this critical issue along with multiple other pre-authentication weaknesses including out-of-bounds write, use-after-free, memory disclosure, denial of service, stack over-read, neighbour-discovery proxy spoofing, HTTP request-smuggling bugs, and DHCPv6 hostname-injection flaws.
- An AI-assisted audit by Hacker House identified additional command-injection, path-traversal, and XSS weaknesses in optional LuCI components that remain under review and were not included in the 24.10.8 release.
- OpenWrt 24.10 is projected to reach end of life in September 2026, with recommendation to migrate to the 25.12 series before then.
Why It Matters
This vulnerability represents a severe security risk for countless IoT and networking devices running OpenWrt, as it enables complete device compromise without authentication from network-adjacent attackers. The combination of root privileges, lack of common mitigations like ASLR and stack canaries in embedded systems, and public proof-of-concept code makes this particularly dangerous for practitioners managing large-scale deployments of OpenWrt-based infrastructure. The simultaneous discovery of multiple vulnerabilities through automated auditing highlights the importance of continuous security testing in open-source firmware projects.
Technical Details
- CVE-2026-53921 affects odhcpd versions containing dhcpv6_ia_handle_IAs() and build_ia() functions, specifically master at commit e432dd6 and all earlier vulnerable versions
- Two distinct overflow paths exist: one triggered by five IA_NA bindings created with an earlier SOLICIT message, another by a single crafted DHCPv6 REQUEST packet sent to UDP port 547
- Both overflow sites occur when crafted IA options leave insufficient space in a fixed 512-byte stack buffer before code appends additional reply data without adequate bounds checking
- The fix implemented checks remaining response-buffer capacity before appending affected data to prevent buffer overflows
- Additional vulnerabilities addressed include CVE-2026-62948 (DHCPv6 hostname-injection causing stored XSS in LuCI leases page) and CVE-2026-62947 (path traversal in cgi-io requiring authenticated session with specific permissions)
- Separate LuCI vulnerabilities identified by Hacker House include directory traversal in luci-app-bmx7, stored XSS in luci-app-olsr, and command injection in luci-app-commands, with some findings potentially executable without authentication under specific configurations
Industry Insight
Security teams managing OpenWrt deployments should prioritize immediate upgrade to version 24.10.8 or 25.12.5, particularly for devices exposed to networks where DHCPv6 services are accessible, given the critical severity and availability of exploit code. Organizations should implement network segmentation to limit access to DHCPv6 services (UDP port 547) from untrusted networks until upgrades can be completed. The discovery process demonstrates the value of combining traditional security audits with AI-assisted analysis, suggesting that organizations should consider integrating automated vulnerability scanning tools into their regular firmware update cycles to identify similar issues proactively before they become critical vulnerabilities.
Disclaimer: The above content is generated by AI and is for reference only.