CVE-2026-46582 is a cache poisoning vulnerability in NLnet Labs Unbound affecting versions 1.6.0 through 1.25.1. During DNSSEC processing, a replayed wildcard RRset can be temporarily accepted as secure based on RRSIG validation alone and written into cache before subsequent NSEC-based wildcard validation correctly determines the response is bogus. In the vulnerable serve-expired reply path, a race between the resolving thread and another thread serving expired data can expose this transient secure state. As a result, a specific sibling record adjacent to a wildcard can be overwritten in cache with the wildcard-derived RRset and marked secure. The flaw arises from incorrect trust being assigned to data before full DNSSEC wildcard validation is complete, combined with cache update behavior on the serve-expired path.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.