Skip to main content
Mallory
MediumVulnerability

CVE-2026-10723: BIND NSEC3 Signer Validation Bypass Allowing Forged NXDOMAIN Responses

Published Jul 22, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days18 mentions · peak 4 in a dayToday
CVSS6.8Medium · v3.1
EPSS0.27%20th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Internet Systems Consortium
IdentifiersCVE-2026-10723CWE-347 · Improper Verification of…

CVE-2026-10723 is a DNSSEC validation vulnerability in BIND 9 caused by incorrect validation of child-zone NSEC3 records and their signers. BIND may accept these records as valid denial-of-existence proofs for existing names in sibling zones, allowing an attacker to forge apparently DNSSEC-authenticated NXDOMAIN responses. Affected versions are 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. F5 BIG-IP DNS is also affected when configured as a recursive resolver with BIND enabled.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation compromises DNS answer integrity by causing a validating resolver to report that an existing name in a sibling zone does not exist. Clients relying on the resolver may consequently be unable to resolve legitimate names, even though the negative response appears DNSSEC-authenticated. Arbitrary code execution, privilege escalation, and sensitive-data disclosure are not established impacts of this vulnerability.

Mitigation

If you can’t patch tonight, do this now.

For F5 BIG-IP DNS, disable BIND in the applicable DNS profile or disable recursion when unnecessary. Disabling BIND can affect configurations using it as a fallback resolution method. Alternatively, restrict recursion to authorized clients to reduce exposure; this does not correct the underlying validation flaw.

Remediation

Patch, then assume compromise.

Install vendor security updates that correct NSEC3 signer validation. Available fixed distribution packages include bind9 1:9.20.26-1~deb13u1 for Debian trixie, 1:9.20.24-1ubuntu0.4 for Ubuntu 26.04 LTS, 1:9.18.39-0ubuntu0.24.04.8 for Ubuntu 24.04 LTS, and 1:9.18.39-0ubuntu0.22.04.7 for Ubuntu 22.04 LTS. Use the applicable vendor-fixed package for other distributions; backported fixes may retain an upstream version number within the affected ranges. For F5 BIG-IP DNS, install a release explicitly documented as fixed when available; the F5 advisory lists no fixed release for the affected 21.x and 17.x branches.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Internet Systems ConsortiumBindapplication
FAQ

Frequently asked questions

Is CVE-2026-10723 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-10723 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-10723?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-10723.
Is there a patch for CVE-2026-10723?
Install vendor security updates that correct NSEC3 signer validation. Available fixed distribution packages include bind9 1:9.20.26-1~deb13u1 for Debian trixie, 1:9.20.24-1ubuntu0.4 for Ubuntu 26.04 LTS, 1:9.18.39-0ubuntu0.24.04.8 for Ubuntu 24.04 LTS, and 1:9.18.39-0ubuntu0.22.04.7 for Ubuntu 22.04 LTS.
What products are affected by CVE-2026-10723?
Internet Systems Consortium Bind.
How severe is CVE-2026-10723?
CVE-2026-10723 has a CVSS v3.1 score of 6.8 (Medium) and an EPSS score of 0.27% (20th percentile) as of Nov 17, 2026.
Activity feed

Recent activity

82 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+62 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity5Community discussion across Reddit, Mastodon, and other social sources.