Skip to main content
Mallory
LowVulnerability

CVE-2026-54478: DNS Cookie source-validation bypass in Unbound PROXY protocol handling

Published Jul 22, 2026 · Updated 3 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 2 in a dayToday
CVSS3.7Low · v3.1
EPSS0.24%15th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Nlnet Labs
IdentifiersCVE-2026-54478CWE-346

NLnet Labs Unbound versions 1.18.0 through 1.25.1 incorrectly bind DNS server cookies to client addresses when a proxy-protocol-port interface is configured with answer-cookie: yes. The RFC 9018 server-cookie SipHash uses the proxy's wire address rather than the client address declared in the PROXYv2 header. Consequently, a server cookie obtained through one proxy node validates for arbitrary declared client sources behind that node. In UDP deployments, an off-path attacker can obtain a cookie with one legitimate query and replay it with spoofed source addresses to bypass DNS Cookie checks.

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.

Exploitation defeats DNS Cookie source-validation protections in affected UDP PROXY-protocol deployments, allowing spoofed-source queries to pass checks intended to reject them. The vulnerability has a low integrity impact; no direct confidentiality or availability impact is established.

Mitigation

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

Until patched, avoid combining proxy-protocol-port with answer-cookie on UDP-facing Unbound deployments. Restrict access to trusted proxy nodes and ensure that only authorized infrastructure can supply PROXYv2 headers.

Remediation

Patch, then assume compromise.

Upgrade Unbound and related packages to version 1.25.2 or later, or install the applicable distribution security update containing the fix. For Debian 13 (trixie), the security-fixed package version is 1.26.1-0+deb13u1.

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.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Nlnet LabsUnboundapplication
FAQ

Frequently asked questions

Is CVE-2026-54478 exploited in the wild?
As of Nov 14, 2026, Mallory has no reports of CVE-2026-54478 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-54478?
As of Nov 14, 2026, Mallory has found no public exploit for CVE-2026-54478.
Is there a patch for CVE-2026-54478?
Upgrade Unbound and related packages to version 1.25.2 or later, or install the applicable distribution security update containing the fix. For Debian 13 (trixie), the security-fixed package version is 1.26.1-0+deb13u1.
What products are affected by CVE-2026-54478?
Nlnet Labs Unbound.
How severe is CVE-2026-54478?
CVE-2026-54478 has a CVSS v3.1 score of 3.7 (Low) and an EPSS score of 0.24% (15th percentile) as of Nov 14, 2026.
Activity feed

Recent activity

8 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 activity3Community discussion across Reddit, Mastodon, and other social sources.