Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2026-55606: Stack Buffer Over-read in OpenWrt odhcpd DUID Length Parsing

Published Oct 23, 2026 · Updated 19 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS6.5Medium · v3.1
EPSS0.47%41st percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2026-55606CWE-126 · Buffer Over-read

CVE-2026-55606 is a moderate-severity vulnerability in OpenWrt's odhcpd DHCP service. The flaw is a stack buffer over-read caused by an endianness mismatch when handling a DHCP Unique Identifier (DUID) length value. Improper interpretation of the DUID length can cause odhcpd to read beyond the intended bounds of a stack buffer while processing attacker-supplied DHCPv6 data. The issue is reachable by a network-adjacent attacker against the default-enabled odhcpd service in affected OpenWrt releases prior to the fixed 25.12.5 update.

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 cause out-of-bounds reads from stack memory in odhcpd during DHCPv6 processing. The primary security consequence indicated is memory-safety failure that may lead to service instability or denial of service. Depending on surrounding implementation details, stack over-read conditions can also expose unintended memory contents to subsequent processing paths, but specific evidence of attacker-observable memory disclosure beyond the over-read itself is not currently available.

Mitigation

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

If immediate patching is not possible, reduce exposure to odhcpd by restricting access to DHCPv6 services to trusted network segments only and disabling IPv6 DHCP functionality where operationally feasible. Limit network adjacency for untrusted clients that can send crafted DHCPv6 traffic to the affected service. These measures only reduce exploitability and do not eliminate the underlying flaw.

Remediation

Patch, then assume compromise.

Upgrade OpenWrt to version 25.12.5 or a later release that includes the odhcpd fix for CVE-2026-55606. The vendor release specifically addresses the DUID length endianness mismatch in odhcpd.

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-55606 exploited in the wild?
As of Oct 29, 2026, Mallory has no reports of CVE-2026-55606 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-55606?
Yes. As of Oct 29, 2026, Mallory has reports of a public exploit for CVE-2026-55606.
Is there a patch for CVE-2026-55606?
Upgrade OpenWrt to version 25.12.5 or a later release that includes the odhcpd fix for CVE-2026-55606. The vendor release specifically addresses the DUID length endianness mismatch in odhcpd.
How severe is CVE-2026-55606?
CVE-2026-55606 has a CVSS v3.1 score of 6.5 (Medium) and an EPSS score of 0.47% (41st percentile) as of Oct 29, 2026.
Activity feed

Recent activity

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

View more in app →
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.