CVE-2026-3119 is a denial-of-service vulnerability in ISC BIND 9's named daemon triggered during processing of an authenticated DNS query containing a TKEY record. The flaw is a NULL pointer dereference in dns_tkey_processquery() in lib/dns/tkey.c. In affected code paths, the keyname variable can remain NULL for TKEY DELETE mode and certain invalid TKEY modes, yet execution continues into response construction where keyname is passed through add_rdata_to_list() to dns_name_copy(). This reaches an assertion that assumes a valid source name, causing a reachable assertion failure and abrupt process termination. The issue affects BIND 9 versions 9.20.0 through 9.20.20, 9.21.0 through 9.21.19, and 9.20.9-S1 through 9.20.20-S1. BIND 9.18.x and 9.18-S1 are not affected.
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 vulnerability in ISC BIND 9 where an authenticated query containing a TKEY record may cause the named process to terminate unexpectedly.
An authenticated denial-of-service vulnerability in BIND named caused by a NULL pointer dereference in `dns_tkey_processquery()` when processing TKEY records. A signed TKEY DELETE request or certain invalid TKEY modes can cause `named` to abort unexpectedly.
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.