Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2026-53921: DHCPv6 stack buffer overflow in OpenWrt odhcpd

Published Oct 23, 2026 · Updated 19 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days6 mentions · peak 4 in a dayToday
CVSS9.8Critical · v3.1
EPSS1.1%67th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2026-53921CWE-121 · Stack-based Buffer Overflow

CVE-2026-53921 is a stack-based buffer overflow in the DHCPv6 Identity Association (IA) response serialization performed by OpenWrt's odhcpd service. A crafted DHCPv6 REQUEST containing enough IA options can nearly exhaust a fixed 512-byte stack buffer, after which additional response data is appended without sufficient bounds checking. Two overflow sites involve build_ia(), which appends an error-status option, and dhcpv6_ia_handle_IAs(), which appends Reconfigure Accept and associated authentication data. An unauthenticated attacker able to reach the DHCPv6 server can trigger memory corruption, potentially causing a service crash or arbitrary code execution with root privileges.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can disrupt DHCPv6 service or execute arbitrary code as root, potentially compromising the router's confidentiality, integrity, and availability. Root-level compromise could expose sensitive configuration and permit modification of routing, firewall, and other device settings. Code execution is more feasible on embedded targets lacking stack canaries and ASLR, but is not guaranteed on every affected platform. The published CVSS v3.1 score is 9.8.

Mitigation

If you can’t patch tonight, do this now.

Until patched, reduce exposure by restricting access to the DHCPv6 server on UDP port 547 to necessary network segments and preventing access from untrusted segments. If operationally acceptable, disable DHCPv6 server functionality on exposed interfaces. Network restrictions do not protect against malicious clients that retain access to the service; patching remains necessary.

Remediation

Patch, then assume compromise.

Install OpenWrt 24.10.8 or 25.12.5, or a later supported release containing the odhcpd fixes. Prefer migration from the 24.10 branch to a supported release. For custom builds, incorporate both response-buffer bounds checks: build_ia() must verify capacity before appending the error-status option, and dhcpv6_ia_handle_IAs() must reserve enough space for Reconfigure Accept and the additional authentication data used by DHCPv6 REQUEST messages.

Public exploits

Exploits

1 exploit validated by Mallory's analysis. Hidden: 2 rejected by Mallory's analysis as not a working exploit.

View more in app →
CVE-2026-53921-PoC-ExploitRepository contains a Python-based exploit and a separate Python verifier for CVE-2026-53921, a claimed stack buffer overflow in OpenWrt's odhcpd DHCPv6 handling. Structure is minimal: README with vulnerability narrative and usage context, exploit.py as the main offensive component, verifier.py as a non-exploit checker, and requirements.txt listing scapy/requests/PySocks/paramiko. exploit.py is the primary entry point and is clearly intended for active exploitation rather than mere detection. It requires root, uses Scapy to craft/send IPv6 DHCPv6 packets, supports single-target or list-based targeting, multithreaded scanning, architecture handling, optional SOCKS proxying, and listener management. The visible code includes hardcoded MIPS shellcode builders for reverse and bind shells and architecture-specific return addresses (generic, ar71xx, ramips), indicating the exploit is tailored toward common OpenWrt router architectures. Based on the exposed imports, argument handling, and control flow, the script can scan for DHCPv6 responsiveness, detect/choose architecture, generate payloads, and attempt exploitation with options such as vector selection, offset tuning, encoding, persistence, and log clearing. verifier.py is a companion detection utility. It does not exploit the target; instead it checks whether DHCPv6 responds on the local link using multicast ff02::1:2 and UDP 546->547, then attempts version inference via HTTP and SSH banner checks. It flags OpenWrt versions before 24.10.8 and 25.12.5 as vulnerable. Fingerprintable targets/endpoints are primarily network-facing: DHCPv6 UDP/547, DHCPv6 multicast ff02::1:2, SSH TCP/22, and HTTP on the target IPv6 host. The exploit is aimed at unauthenticated remote network exploitation over IPv6 against vulnerable OpenWrt/odhcpd instances, with the intended outcome of root-level shell access.tc4dy · Disclosed Jul 28, 2026 · python · network · wirelessOperational
FAQ

Frequently asked questions

Is CVE-2026-53921 exploited in the wild?
As of Oct 29, 2026, Mallory has no reports of CVE-2026-53921 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-53921?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-53921, the earliest disclosed Jul 28, 2026.
Is there a patch for CVE-2026-53921?
Install OpenWrt 24.10.8 or 25.12.5, or a later supported release containing the odhcpd fixes. Prefer migration from the 24.10 branch to a supported release.
How severe is CVE-2026-53921?
CVE-2026-53921 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 1.1% (67th percentile) as of Oct 29, 2026.
Activity feed

Recent activity

34 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
cvefeed high severityNews · Oct 23, 2026CVE-2026-53921 - odhcpd: Stack buffer overflow in DHCPv6 IA reply serialization (2 independent sites)A stack-based buffer overflow in OpenWrt's odhcpd before version 25.12. Two independent overflow sites in the same call chain are reachable through a single unauthenticated UDP packet containing a crafted DHCPv6 REQUEST. Because odhcpd runs as root and embedded targets often lack stack canaries and ASLR, exploitation could realistically enable root-level code execution. Version 25.12 contains a patch; the content does not report actual exploitation.Read more ↗xakepNews · Aug 3, 2026В OpenWrt исправили критическую уязвимость в DHCPv6-сервере - ХакерКритическая уязвимость удаленного выполнения кода в компоненте OpenWrt odhcpd (DHCPv6-сервер), вызванная переполнением буфера при обработке специально сформированного DHCPv6 REQUEST, что позволяет неаутентифицированному атакующему выполнить код с правами root.Read more ↗scworldNews · Jul 29, 2026OpenWrt releases security updates for critical DHCPv6 flaw and other vulnerabilities | brief | SC MediaA critical unauthenticated stack buffer overflow in OpenWrt's odhcpd DHCPv6 service that can be triggered remotely via a crafted DHCPv6 REQUEST and could lead to code execution on devices lacking protections like stack canaries and ASLR.Read more ↗the hacker newsNews · Jul 28, 2026Critical OpenWrt DHCPv6 Flaw Could Let Unauthenticated Attackers Run Code as RootA critical stack-based buffer overflow in OpenWrt's odhcpd DHCPv6 request-processing path that can be triggered remotely without authentication and may realistically lead to code execution as root on embedded devices.Read more ↗
+4 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity26Community discussion across Reddit, Mastodon, and other social sources.