Loading vulnerability…
CVE-2026-10723 is an insufficient verification of data authenticity vulnerability in BIND 9 DNSSEC validation. BIND may accept a child-zone NSEC3 record as valid when the record's signer name does not match the zone that owns it. This incorrect acceptance can enable NSEC3 impersonation and the forgery of authenticated NXDOMAIN responses. Affected versions are BIND 9.18.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.
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.
33 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability addressed by Fedora advisory 2026-0adbf9c133; the content provides no technical flaw description.
A vulnerability referenced by an Alibaba Cloud Linux 3 security update for BIND-related packages; no technical flaw description is provided.
A vulnerability addressed by the Fedora 43 BIND security advisory; no technical flaw details are provided.
A vulnerability addressed by the Fedora 2026-d87e7f498a update. No technical flaw details are provided.
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.