Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-53918: Heap use-after-free in OpenWrt odhcpd DHCPv6 IA handling

Published Oct 23, 2026 · Updated 18 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS8.8High · v4
EPSS0.62%50th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2026-53918CWE-416 · Use After Free

CVE-2026-53918 is a heap-use-after-free vulnerability in the DHCPv6 Identity Association (IA) handler of odhcpd, the DHCPv6, DHCPv4, and router-advertisement server used by OpenWrt. Versions before 25.12 maintain a per-message first-lease pointer to share a Reconfigure authentication key among IA options. A crafted DHCPv6 REQUEST can establish this pointer, then use a later IA option with the same IAID to fail an on-link check and free the referenced lease without clearing the pointer. A subsequent IA option allocates another lease and copies the authentication key through the dangling pointer, causing a 16-byte read from freed heap memory. The vulnerability enables denial of service and Reconfigure/ForceRenew authentication-key confusion.

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.

An unauthenticated network-adjacent attacker can disrupt odhcpd service availability and cause DHCPv6 Reconfigure/ForceRenew authentication-key confusion. AddressSanitizer confirmed the use-after-free, and native tracing demonstrated deterministic reuse of the freed lease by the destination allocation, resulting in a zeroed Reconfigure key copy. Arbitrary program-counter control or code execution has not been demonstrated for this vulnerability alone; confidentiality compromise is not established.

Mitigation

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

Until patched, consider disabling odhcpd's DHCPv6 server functionality on interfaces accessible to untrusted clients, where operationally feasible, or restricting DHCPv6 access to trusted network segments. These exposure-reduction measures are not substitutes for the patch; no independently validated workaround is specified.

Remediation

Patch, then assume compromise.

Upgrade odhcpd to version 25.12 or later containing the fix. For OpenWrt deployments, install a firmware release incorporating the patched odhcpd package; OpenWrt 25.12.5 and 24.10.8 include fixes for this CVE. Prefer a currently supported OpenWrt release rather than remaining on the 24.10 series.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-53918 exploited in the wild?
As of Oct 30, 2026, Mallory has no reports of CVE-2026-53918 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-53918?
Yes. As of Oct 30, 2026, Mallory has reports of a public exploit for CVE-2026-53918.
Is there a patch for CVE-2026-53918?
Upgrade odhcpd to version 25.12 or later containing the fix. For OpenWrt deployments, install a firmware release incorporating the patched odhcpd package; OpenWrt 25.12.5 and 24.10.8 include fixes for this CVE.
How severe is CVE-2026-53918?
CVE-2026-53918 has a CVSS v4 score of 8.8 (High) and an EPSS score of 0.62% (50th percentile) as of Oct 30, 2026.
Activity feed

Recent activity

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

View more in app →
+1 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 activity1Community discussion across Reddit, Mastodon, and other social sources.