CVE-2026-44608 is a locking inconsistency vulnerability in NLnet Labs Unbound affecting versions 1.14.0 through 1.25.0 inclusive. In multi-threaded deployments using Response Policy Zones (RPZ), a race condition can occur during RPZ zone transfer reload processing when the RPZ zone contains rpz-nsip or rpz-nsdname triggers. Under these conditions, a reader thread may not retain the relevant lock long enough while another thread applying an XFR-based RPZ reload frees objects that the reader is still about to traverse, resulting in a heap use-after-free in the RPZ code. The flaw does not affect RPZ data loaded from local files. Unbound 1.25.1 fixes the issue by correcting the locking behavior.
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 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.