CVE-2026-80225 is a medium-severity uncontrolled resource-consumption vulnerability in NLnet Labs Unbound through version 1.26.0. The TCP and DNS-over-TLS reading procedure imposes no limit on consecutive reads from a connection. A client can continuously submit distinct, uncached DNS names such that its writes remain ahead of Unbound's processing drain, causing one resolver worker to spend its entire event loop servicing that connection rather than other work.
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.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A medium-severity Unbound service-degradation vulnerability triggered by sustained distinct uncached DNS-name requests over a single TCP or DNS-over-TLS connection.
A potential denial-of-service condition caused by continuous queries over a single TCP or DNS-over-TLS connection.
A potential denial-of-service condition in Unbound caused by continuous queries over a single TCP or DNS-over-TLS connection.
A potential denial-of-service issue in Unbound caused by continuous queries on a single TCP or DNS-over-TLS connection.
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.