Is CVE-2026-10723 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-10723 being exploited in the wild.

How severe is CVE-2026-10723?

Medium severity, with a CVSS score of 6.8, published 22 July 2026.

Which products and versions are affected?

Isc BIND 9 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, 9.20.9-S1 through 9.20.24-S1.

Is there a fix for CVE-2026-10723?

A patch was published on 2026-07-22: Fixed versions released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-10723 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-10723?

Check whether you run Isc BIND 9 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-10723: ISC BIND incorrect NSEC3 record validation

CVE-2026-10723 · Severity: medium · CVSS 6.8 · Published 2026-07-22

BIND is a widely used software suite for managing the Domain Name System (DNS), which translates human-readable web addresses into IP addresses. A vulnerability has been identified where BIND may incorrectly validate security records from child zones. This could allow a remote attacker to forge responses that falsely claim a legitimate website or service does not exist, potentially disrupting access to digital services or redirecting traffic.

Technologies: Isc BIND 9. Vendors: Isc.

Quick answers

Is CVE-2026-10723 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-10723 being exploited in the wild.
How severe is CVE-2026-10723?: Medium severity, with a CVSS score of 6.8, published 22 July 2026.
Which products and versions are affected?: Isc BIND 9 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, 9.20.9-S1 through 9.20.24-S1.
Is there a fix for CVE-2026-10723?: A patch was published on 2026-07-22: Fixed versions released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-10723 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-10723?: Check whether you run Isc BIND 9 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A vulnerability exists in BIND 9's handling of DNSSEC NSEC3 records. The software may incorrectly accept NSEC3 records from a child zone as valid even when they are malformed or incorrect. An unauthenticated remote attacker can exploit this by providing forged NSEC3 records, allowing them to generate authenticated NXDOMAIN (non-existent domain) responses for sibling zones. This is classified as a cryptographic signature verification failure (CWE-347). The attack requires specific timing or network conditions (AC:H) but can impact the integrity of DNS data across security boundaries. Patches are available in versions 9.20.26, 9.21.24, and 9.20.26-S1.

Affected products

ISC BIND 9 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, 9.20.9-S1 through 9.20.24-S1

Timeline

2026-07-15: other: Early notification issued
2026-07-22: advisory: Public disclosure of CVE-2026-10723
2026-07-22: patched: Fixed versions released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.