CVE-2026-10723: Incorrect acceptance of NSEC3 records

Published Jul 21, 2026
·
Updated

BIND may accept incorrect child-zone NSEC3 records as valid, allowing forged authenticated NXDOMAIN responses for sibling zones. AC:H (high complexity) keeps severity at Medium despite S:C.

Other sources

BIND may accept incorrect child-zone NSEC3 records as valid, which could allow an attacker to forge authenticated NXDOMAIN responses. This issue affects BIND 9 versions 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.

— MITRE

Affected Software

17 affected componentsFixes available
ISC BIND 9>=9.18.0<=9.18.50, >=9.20.0<=9.20.24, >=9.21.0<=9.21.23, >=9.11.3-S1<=9.18.50-S1, >=9.20.9-S1<=9.20.24-S1
Microsoft azl3 bind 9.20.23-1<9.20.26-1
9.20.26-1
F5 BIG-IP (DNS)=21.1.0
21.1.0.3
F5 BIG-IP (DNS)>=17.5.0<=17.5.1, >=17.1.0<=17.1.3
17.5.1.1017.1.3.6
ISC BIND>=9.11.3<=9.18.50
ISC BIND>=9.18.0<=9.18.50
ISC BIND>=9.20.0<=9.20.24
ISC BIND>=9.20.9<=9.20.24
ISC BIND>=9.21.0<=9.21.23
alpine/bind>=9.11.3<9.20.26-r0
9.20.26-r0
alpine/bind>=9.11.3<9.20.26-r0
9.20.26-r0
alpine/bind>=9.11.3<9.20.26-r0
9.20.26-r0
debian/bind9<1:9.18.49-1~deb12u2
1:9.18.49-1~deb12u2
debian/bind9<1:9.20.26-1~deb13u1
1:9.20.26-1~deb13u1
debian/bind9<1:9.20.26-1
1:9.20.26-1
debian/bind9<=1:9.18.49-1~deb12u1
1:9.18.49-1~deb12u31:9.20.26-1~deb13u11:9.20.30-1~deb13u11:9.20.30-1
IBM API Connect V12 OnPrem<=v12.1.0.0 - v12.1.1.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 9.20.26-1
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 21.1.0.3
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 17.5.1.1017.1.3.6
  4. Upgrade

    Upgrade alpine/bind to a version that resolves this vulnerability.

    Fixed in 9.20.26-r0
  5. Upgrade

    Upgrade debian/bind9 to a version that resolves this vulnerability.

    Fixed in 1:9.18.49-1~deb12u2
  6. Upgrade

    Upgrade debian/bind9 to a version that resolves this vulnerability.

    Fixed in 1:9.20.26-1~deb13u1
  7. Upgrade

    Upgrade debian/bind9 to a version that resolves this vulnerability.

    Fixed in 1:9.20.26-1
  8. Upgrade

    Upgrade debian/bind9 to a version that resolves this vulnerability.

    Fixed in 1:9.18.49-1~deb12u3Fixed in 1:9.20.26-1~deb13u1Fixed in 1:9.20.30-1~deb13u1Fixed in 1:9.20.30-1
  9. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch CVE-2026-10723
  10. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch CVE-2026-10822
  11. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch CVE-2026-11331
  12. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch CVE-2026-11605
  13. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch CVE-2026-11622
  14. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch CVE-2026-11721
  15. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch CVE-2026-12617
  16. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch CVE-2026-13204
  17. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch CVE-2026-13321
  18. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 9.20.26
  19. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 9.21.24
  20. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 9.20.26-S1

Event History

Jul 21, 2026
Data Sourced
via Red Hat·09:17 PM
DescriptionSeverityAffected Software
Jul 22, 2026
CVE Published
via MITRE·02:08 PM
Data Sourced
via MITRE·02:08 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·03:16 PM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·03:16 PM
DescriptionSeverityAffected Software
Jul 25, 2026
Data Sourced
via Microsoft·08:04 AM
DescriptionSeverityWeaknessAffected Software
Oct 8, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software
Oct 14, 2026
Advisory Published
via F5·03:42 PM
Data Sourced
via F5·03:42 PM
DescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2026-10723?

CVE-2026-10723 has a medium severity rating of 6.8.

2

How do I fix CVE-2026-10723?

To fix CVE-2026-10723, upgrade to the latest version of BIND that resolves this vulnerability.

3

What types of records are affected by CVE-2026-10723?

CVE-2026-10723 affects the incorrect acceptance of child-zone NSEC3 records.

4

What impact can an attacker have with CVE-2026-10723?

An attacker could potentially forge authenticated NXDOMAIN responses, misleading clients about the existence of domains.

5

Which versions of BIND are affected by CVE-2026-10723?

BIND versions 9.18.0 through 9.18.50, 9.20.0 through 9.20.24, and others listed in the vulnerability details are affected.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203