CVE-2026-19941 is an improper DNSSEC proof-validation flaw in BIND 9 named resolvers. The resolver's checkwildcard() logic can accept an out-of-zone or otherwise inapplicable NSEC record as proof that no wildcard record exists. This permits an attacker positioned at the same level as, or an upstream level of, the target zone name to make the resolver incorrectly conclude that a victim wildcard DNS record is absent. Affected versions include BIND 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, and the corresponding affected Supported Preview Edition releases.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A BIND 9 `named` resolver flaw in which an inapplicable DNSSEC NSEC record can be accepted as proof that a wildcard record does not exist, enabling an attacker at the same or upstream zone level to mask a victim wildcard DNS record.
A medium-severity remote BIND 9 resolver flaw in checkwildcard() that accepts an out-of-zone or otherwise inapplicable NSEC record as proof that a wildcard does not exist. An attacker controlling a same-level or upstream zone may suppress a victim wildcard mapping and cause cache poisoning.
An unpatched vulnerability affecting Debian Linux 12.0, 13.0, and 14.0. The supplied CVSS v3.0 vector indicates network reachability, high attack complexity, no privileges or user interaction required, and an integrity impact 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.