Skip to main content
Mallory
LowVulnerability

CVE-2026-46582: DNSSEC wildcard replay cache poisoning in Unbound's serve-expired path

Published Jul 22, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days8 mentions · peak 2 in a dayToday
CVSS3.7Low · v3.1
EPSS0.19%9th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Nlnet Labs
IdentifiersCVE-2026-46582CWE-362

NLnet Labs Unbound versions 1.6.0 through 1.25.1 contain a DNSSEC validation race condition affecting the serve-expired reply path. A replayed, signed wildcard RRset can temporarily be marked secure and update a cached sibling record after RRSIG validation but before NSEC-based wildcard validation completes. During this interval, another thread serving an expired answer can consume the updated RRset and its secure status. Subsequent validation marks the triggering response bogus, but the poisoned RRset can already be used to answer queries, substituting wildcard-derived data for an existing specific record.

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 compromises DNS answer integrity by replacing a specific cached record with data from a wildcard that could otherwise cover that name. The substituted RRset can be treated as DNSSEC secure even though complete validation rejects the triggering response. The demonstrated impact is limited DNS cache poisoning; confidentiality loss, code execution, and service disruption are not established for this vulnerability.

Mitigation

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

Disable serve-expired functionality until a fixed package can be installed, removing the reply path required for exploitation. This is a mechanism-based workaround; no vulnerability-specific vendor workaround is identified.

Remediation

Patch, then assume compromise.

Upgrade to a security-fixed Unbound release newer than 1.25.1, or install the operating-system vendor's package update addressing CVE-2026-46582. For Debian 13 (trixie), upgrade to version 1.26.1-0+deb13u1 or later.

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-46582 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-46582 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-46582?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-46582.
Is there a patch for CVE-2026-46582?
Upgrade to a security-fixed Unbound release newer than 1.25.1, or install the operating-system vendor's package update addressing CVE-2026-46582. For Debian 13 (trixie), upgrade to version 1.26.1-0+deb13u1 or later.
What products are affected by CVE-2026-46582?
Nlnet Labs Unbound.
How severe is CVE-2026-46582?
CVE-2026-46582 has a CVSS v3.1 score of 3.7 (Low) and an EPSS score of 0.19% (9th percentile) as of Nov 17, 2026.
Activity feed

Recent activity

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

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