Loading vulnerability…
CVE-2026-82717 is a heap-based buffer overflow in NLnet Labs Unbound through version 1.26.0. During CNAME synthesis of an upstream DNS response, Unbound may rewrite an enforced maximum TTL in the packet buffer. A crafted DNS compression pointer referencing the overwritten value can invalidate the domain name and enter an error path that fails to correctly advance the packet-buffer position. Subsequent processing progressively corrupts heap memory and can overflow the heap buffer.
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.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity heap-corruption flaw in Unbound CNAME synthesis during upstream-response processing. It can cause denial of service and may permit remote code execution under certain system and compilation configurations.
A heap-corruption vulnerability reachable through CNAME synthesis.
A heap-corruption vulnerability in Unbound CNAME synthesis.
An Unbound flaw in CNAME synthesis that can cause heap corruption.
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.