Loading vulnerability…
CVE-2026-50251 affects NLnet Labs Unbound up to and including version 1.25.1. When the unwanted-reply-threshold setting is enabled with a value greater than zero, an attacker who controls a delegation can return in-bailiwick glue records containing 0.0.0.0 or ::. On systems that route such traffic back to the resolver, Unbound's iterator follows the glue and receives a reply from a different source address than the original queried address, causing the response to be classified as an unwanted reply. This increments the unwanted reply counter until the configured threshold is reached, which triggers Unbound's defensive cache-clearing behavior. Because the counter resets after each cache flush, the condition can be re-triggered indefinitely, creating a persistent loop of cache eviction without requiring spoofed packets.
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.