CVE-2026-13321

The BIND resolver accepts validly-signed NSEC records where the "Next Domain Name" field points outside the signer's zone. This issue affects BIND 9 versions 9.11.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.

The BIND resolver accepts validly-signed NSEC records where the "Next Domain Name" field points outside the signer's zone. This issue affects BIND 9 versions 9.11.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.

BIND (Berkeley Internet Name Domain) is an implementation of the DNS (Domain Name System) protocols. BIND includes a DNS server (named), which resolves host names to IP addresses; a resolver library (routines for applications to use when interfacing with DNS); and tools for verifying that the DNS server is operating properly.

Security Fix(es):

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.(CVE-2026-10723)

If BIND encounters a particular invalid data structure in a DNS record, it will accept the invalid data, and may subsequently abort and exit.

BIND will first need to store a DNS record for a key (KEY, DNSKEY, etc.). That key must specify a PRIVATEDNS algorithm (253), and in the algorithm identifier, improperly give a length longer than the actual identifier data. The invalid identifier will be stored. If BIND later needs to render that record to text, it will use the invalid length during processing, leading to a consistency check failing. 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.18.11-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.(CVE-2026-10822)

An attacker who knows (or guesses) that a resolver uses RPZ with wildcard CNAME policies can craft query names long enough to trigger a NAMETOOLONG error condition during RPZ processing. This is not handled correctly and may lead to defeating the RPZ rule. It also may lead to an unexpected exit of the BIND 9 software. This issue affects BIND 9 versions 9.16.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.16.8-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.(CVE-2026-11331)

It is possible for an attacker's zone to respond to a query with an RRSIG that has a smaller number of labels than the zone in which the RRSIG is contained. This causes named to produce a wildcard name for a zone that is shorter than the attacker's zone, which can result in cache poisoning. For this attack to have any effect, the resolver under attack must have set synth-from-dnssec yes; (which is the default). This issue affects BIND 9 versions 9.11.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.(CVE-2026-11721)

The issue is unexpected program termination based on ordering and/or specific content in responses to queries for CNAME or DNAME, and A records. Specifically, if a client queries for a DNAME and A record below the DNAME to the resolver, and the authoritative server responds positively to the A query but delays the DNAME response and later responds negatively, named may quit unexpectedly. Or, if a client queries for a CNAME and A record for the same name to the resolver, and the authoritative server responds positively to the A query but delays the CNAME response and later responds with a self-referential CNAME, the same failure may occur. This issue affects BIND 9 versions 9.18.0 through 9.18.50, 9.20.0 through 9.20.24, 9.18.11-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.(CVE-2026-12617)

If a provably insecure domain is covered by both an NSEC and NSEC3 record at the parent, and there exist an RRSIG for only one of these types, then BIND may exit unexpectedly with an assertion while validating this proof. This issue affects BIND 9 versions 9.11.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.(CVE-2026-13204)

The BIND resolver accepts validly-signed NSEC records where the "Next Domain Name" field points outside the signer's zone. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through…

BIND (Berkeley Internet Name Domain) is an implementation of the DNS (Domain Name System) protocols. BIND includes a DNS server (named), which resolves host names to IP addresses; a resolver library (routines for applications to use when interfacing with DNS); and tools for verifying that the DNS server is operating properly.

Security Fix(es):

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.(CVE-2026-10723)

If BIND encounters a particular invalid data structure in a DNS record, it will accept the invalid data, and may subsequently abort and exit.

BIND will first need to store a DNS record for a key (KEY, DNSKEY, etc.). That key must specify a PRIVATEDNS algorithm (253), and in the algorithm identifier, improperly give a length longer than the actual identifier data. The invalid identifier will be stored. If BIND later needs to render that record to text, it will use the invalid length during processing, leading to a consistency check failing. 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.18.11-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.(CVE-2026-10822)

An attacker who knows (or guesses) that a resolver uses RPZ with wildcard CNAME policies can craft query names long enough to trigger a NAMETOOLONG error condition during RPZ processing. This is not handled correctly and may lead to defeating the RPZ rule. It also may lead to an unexpected exit of the BIND 9 software. This issue affects BIND 9 versions 9.16.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.16.8-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.(CVE-2026-11331)

The issue is a resource exhaustion vulnerability associated with DNSSEC validation. BIND always validates all RRSIG records in an answer, even if they are not strictly needed. A query to an authoritative server/zone which returns many valid but superfluous RRSIG records causes the validator to waste disproportionate CPU time. This issue affects BIND 9 versions 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, and 9.20.9-S1 through 9.20.24-S1.(CVE-2026-11605)

A DNSSEC validating resolver that is under a random subdomain attack against a DNSSEC-signed zone can suffer from runaway memory usage. The attacker needs to be able to send queries faster than the resolver can perform validation. The increased memory usage can be orders of magnitude beyond the limit configured in the max-cache-size parameter. This issue affects BIND 9 versions 9.11.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.(CVE-2026-11622)

It is possible for an attacker's zone to respond to a query with an RRSIG that has a smaller number of labels than the zone in which the RRSIG is contained. This causes named to produce a wildcard name for a zone that is shorter than the attacker's zone, which can result in cache poisoning. For this attack to have any effect, the resolver under attack must have set synth-from-dnssec yes; (which is the default). This issue affects BIND 9 versions 9.11.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.(CVE-2026-11721)

The issue is unexpected program termination based on ordering and/or specific content in responses to queries for CNAME or DNAME, and A records. Specifically, if a client queries for a DNAME and A record below the DNAME to the resolver, and the authoritative server responds positively to the A query but delays the DNAME response and later responds negatively, named may quit unexpectedly. Or, if a client queries for a CNAME and A record for the same name to the…

BIND (Berkeley Internet Name Domain) is an implementation of the DNS (Domain Name System) protocols. BIND includes a DNS server (named), which resolves host names to IP addresses; a resolver library (routines for applications to use when interfacing with DNS); and tools for verifying that the DNS server is operating properly.

Security Fix(es):

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.(CVE-2026-10723)

If BIND encounters a particular invalid data structure in a DNS record, it will accept the invalid data, and may subsequently abort and exit.

BIND will first need to store a DNS record for a key (KEY, DNSKEY, etc.). That key must specify a PRIVATEDNS algorithm (253), and in the algorithm identifier, improperly give a length longer than the actual identifier data. The invalid identifier will be stored. If BIND later needs to render that record to text, it will use the invalid length during processing, leading to a consistency check failing. 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.18.11-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.(CVE-2026-10822)

An attacker who knows (or guesses) that a resolver uses RPZ with wildcard CNAME policies can craft query names long enough to trigger a NAMETOOLONG error condition during RPZ processing. This is not handled correctly and may lead to defeating the RPZ rule. It also may lead to an unexpected exit of the BIND 9 software. This issue affects BIND 9 versions 9.16.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.16.8-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.(CVE-2026-11331)

It is possible for an attacker's zone to respond to a query with an RRSIG that has a smaller number of labels than the zone in which the RRSIG is contained. This causes named to produce a wildcard name for a zone that is shorter than the attacker's zone, which can result in cache poisoning. For this attack to have any effect, the resolver under attack must have set synth-from-dnssec yes; (which is the default). This issue affects BIND 9 versions 9.11.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.(CVE-2026-11721)

The issue is unexpected program termination based on ordering and/or specific content in responses to queries for CNAME or DNAME, and A records. Specifically, if a client queries for a DNAME and A record below the DNAME to the resolver, and the authoritative server responds positively to the A query but delays the DNAME response and later responds negatively, named may quit unexpectedly. Or, if a client queries for a CNAME and A record for the same name to the resolver, and the authoritative server responds positively to the A query but delays the CNAME response and later responds with a self-referential CNAME, the same failure may occur. This issue affects BIND 9 versions 9.18.0 through 9.18.50, 9.20.0 through 9.20.24, 9.18.11-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.(CVE-2026-12617)

If a provably insecure domain is covered by both an NSEC and NSEC3 record at the parent, and there exist an RRSIG for only one of these types, then BIND may exit unexpectedly with an assertion while validating this proof. This issue affects BIND 9 versions 9.11.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.(CVE-2026-13204)

The BIND resolver accepts validly-signed NSEC records where the "Next Domain Name" field points outside the signer's zone. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through…

BIND (Berkeley Internet Name Domain) is an implementation of the DNS (Domain Name System) protocols. BIND includes a DNS server (named), which resolves host names to IP addresses; a resolver library (routines for applications to use when interfacing with DNS); and tools for verifying that the DNS server is operating properly.

Security Fix(es):

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.(CVE-2026-10723)

A DNSSEC validating resolver that is under a random subdomain attack against a DNSSEC-signed zone can suffer from runaway memory usage. The attacker needs to be able to send queries faster than the resolver can perform validation. The increased memory usage can be orders of magnitude beyond the limit configured in the max-cache-size parameter. This issue affects BIND 9 versions 9.11.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.(CVE-2026-11622)

It is possible for an attacker's zone to respond to a query with an RRSIG that has a smaller number of labels than the zone in which the RRSIG is contained. This causes named to produce a wildcard name for a zone that is shorter than the attacker's zone, which can result in cache poisoning. For this attack to have any effect, the resolver under attack must have set synth-from-dnssec yes; (which is the default). This issue affects BIND 9 versions 9.11.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.(CVE-2026-11721)

If a provably insecure domain is covered by both an NSEC and NSEC3 record at the parent, and there exist an RRSIG for only one of these types, then BIND may exit unexpectedly with an assertion while validating this proof. This issue affects BIND 9 versions 9.11.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.(CVE-2026-13204)

The BIND resolver accepts validly-signed NSEC records where the "Next Domain Name" field points outside the signer's zone. This issue affects BIND 9 versions 9.11.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.(CVE-2026-13321)

BIND (Berkeley Internet Name Domain) is an implementation of the DNS (Domain Name System) protocols. BIND includes a DNS server (named), which resolves host names to IP addresses; a resolver library (routines for applications to use when interfacing with DNS); and tools for verifying that the DNS server is operating properly.

Security Fix(es):

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.(CVE-2026-10723)

An attacker who knows (or guesses) that a resolver uses RPZ with wildcard CNAME policies can craft query names long enough to trigger a NAMETOOLONG error condition during RPZ processing. This is not handled correctly and may lead to defeating the RPZ rule. It also may lead to an unexpected exit of the BIND 9 software. This issue affects BIND 9 versions 9.16.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.16.8-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.(CVE-2026-11331)

A DNSSEC validating resolver that is under a random subdomain attack against a DNSSEC-signed zone can suffer from runaway memory usage. The attacker needs to be able to send queries faster than the resolver can perform validation. The increased memory usage can be orders of magnitude beyond the limit configured in the max-cache-size parameter. This issue affects BIND 9 versions 9.11.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.(CVE-2026-11622)

It is possible for an attacker's zone to respond to a query with an RRSIG that has a smaller number of labels than the zone in which the RRSIG is contained. This causes named to produce a wildcard name for a zone that is shorter than the attacker's zone, which can result in cache poisoning. For this attack to have any effect, the resolver under attack must have set synth-from-dnssec yes; (which is the default). This issue affects BIND 9 versions 9.11.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.(CVE-2026-11721)

If a provably insecure domain is covered by both an NSEC and NSEC3 record at the parent, and there exist an RRSIG for only one of these types, then BIND may exit unexpectedly with an assertion while validating this proof. This issue affects BIND 9 versions 9.11.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.(CVE-2026-13204)

The BIND resolver accepts validly-signed NSEC records where the "Next Domain Name" field points outside the signer's zone. This issue affects BIND 9 versions 9.11.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.(CVE-2026-13321)

The Berkeley Internet Name Domain (BIND) is an implementation of the Domain Name System (DNS) protocols. BIND includes a DNS server (named); a resolver library (routines for applications to use when interfacing with DNS); and tools for verifying that the DNS server is operating correctly.

Security Fix(es):

• bind9: bind: Potential wildcard CNAME RPZ policy bypass (CVE-2026-11331)

• bind: bind9: DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field (CVE-2026-13321)

• bind: bind9: Potential memory usage beyond configured limits (CVE-2026-11622)

• bind: bind9: Cache poisoning via label count discrepancy, RRSIG, wildcards (CVE-2026-11721)

• bind: bind9: Unexpected exit with NSEC and NSEC3 both present (CVE-2026-13204)

• bind: bind9: Incorrect acceptance of NSEC3 records (CVE-2026-10723)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The Berkeley Internet Name Domain (BIND) is an implementation of the Domain Name System (DNS) protocols. BIND includes a DNS server (named); a resolver library (routines for applications to use when interfacing with DNS); and tools for verifying that the DNS server is operating correctly.

Security Fix(es):

• bind9: bind: Potential wildcard CNAME RPZ policy bypass (CVE-2026-11331)

• bind: bind9: DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field (CVE-2026-13321)

• bind: bind9: Potential memory usage beyond configured limits (CVE-2026-11622)

• bind: bind9: Cache poisoning via label count discrepancy, RRSIG, wildcards (CVE-2026-11721)

• bind: bind9: Unexpected exit with NSEC and NSEC3 both present (CVE-2026-13204)

• bind: bind9: Incorrect acceptance of NSEC3 records (CVE-2026-10723)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The Berkeley Internet Name Domain (BIND) is an implementation of the Domain Name System (DNS) protocols. BIND includes a DNS server (named); a resolver library (routines for applications to use when interfacing with DNS); and tools for verifying that the DNS server is operating correctly.

Security Fix(es):

• bind: bind9: DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field (CVE-2026-13321)

• bind: bind9: Potential memory usage beyond configured limits (CVE-2026-11622)

• bind: bind9: Cache poisoning via label count discrepancy, RRSIG, wildcards (CVE-2026-11721)

• bind: bind9: Unexpected exit with NSEC and NSEC3 both present (CVE-2026-13204)

• bind: bind9: Incorrect acceptance of NSEC3 records (CVE-2026-10723)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The Berkeley Internet Name Domain (BIND) is an implementation of the Domain Name System (DNS) protocols. BIND includes a DNS server (named); a resolver library (routines for applications to use when interfacing with DNS); and tools for verifying that the DNS server is operating correctly.

Security Fix(es):

• bind9: bind: Potential wildcard CNAME RPZ policy bypass (CVE-2026-11331)

• bind: bind9: DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field (CVE-2026-13321)

• bind: bind9: Potential memory usage beyond configured limits (CVE-2026-11622)

• bind: bind9: Cache poisoning via label count discrepancy, RRSIG, wildcards (CVE-2026-11721)

• bind: bind9: Unexpected exit with NSEC and NSEC3 both present (CVE-2026-13204)

• bind: bind9: Incorrect acceptance of NSEC3 records (CVE-2026-10723)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

BIND (Berkeley Internet Name Domain) is an implementation of the DNS (Domain Name System) protocols. BIND includes a DNS server (named), which resolves host names to IP addresses; a resolver library (routines for applications to use when interfacing with DNS); and tools for verifying that the DNS server is operating properly.

Security Fix(es):

• bind9: bind: Potential wildcard CNAME RPZ policy bypass (CVE-2026-11331)

• bind: bind9: DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field (CVE-2026-13321)

• bind: bind9: Potential memory usage beyond configured limits (CVE-2026-11622)

• bind: bind9: Cache poisoning via label count discrepancy, RRSIG, wildcards (CVE-2026-11721)

• bind: bind9: Unexpected exit with NSEC and NSEC3 both present (CVE-2026-13204)

• bind: bind9: Incorrect acceptance of NSEC3 records (CVE-2026-10723)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The BIND resolver accepts validly-signed NSEC records where the "Next Domain Name" field points outside the signer's zone. This issue affects BIND 9 versions 9.11.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.

The Berkeley Internet Name Domain (BIND) is an implementation of the Domain Name System (DNS) protocols. BIND includes a DNS server (named); a resolver library (routines for applications to use when interfacing with DNS); and tools for verifying that the DNS server is operating correctly.

Security Fix(es):

• bind9: bind: Potential wildcard CNAME RPZ policy bypass (CVE-2026-11331)
• bind: bind9: DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field (CVE-2026-13321)
• bind: bind9: Potential memory usage beyond configured limits (CVE-2026-11622)
• bind: bind9: Cache poisoning via label count discrepancy, RRSIG, wildcards (CVE-2026-11721)
• bind: bind9: Unexpected exit with NSEC and NSEC3 both present (CVE-2026-13204)
• bind: bind9: Incorrect acceptance of NSEC3 records (CVE-2026-10723)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The Berkeley Internet Name Domain (BIND) is an implementation of the Domain Name System (DNS) protocols. BIND includes a DNS server (named); a resolver library (routines for applications to use when interfacing with DNS); and tools for verifying that the DNS server is operating correctly.

Security Fix(es):

• bind9: bind: Potential wildcard CNAME RPZ policy bypass (CVE-2026-11331)
• bind: bind9: DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field (CVE-2026-13321)
• bind: bind9: Potential memory usage beyond configured limits (CVE-2026-11622)
• bind: bind9: Cache poisoning via label count discrepancy, RRSIG, wildcards (CVE-2026-11721)
• bind: bind9: Unexpected exit with NSEC and NSEC3 both present (CVE-2026-13204)
• bind: bind9: Incorrect acceptance of NSEC3 records (CVE-2026-10723)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The Berkeley Internet Name Domain (BIND) is an implementation of the Domain Name System (DNS) protocols. BIND includes a DNS server (named); a resolver library (routines for applications to use when interfacing with DNS); and tools for verifying that the DNS server is operating correctly.

Security Fix(es):

• bind: bind9: DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field (CVE-2026-13321)
• bind: bind9: Potential memory usage beyond configured limits (CVE-2026-11622)
• bind: bind9: Cache poisoning via label count discrepancy, RRSIG, wildcards (CVE-2026-11721)
• bind: bind9: Unexpected exit with NSEC and NSEC3 both present (CVE-2026-13204)
• bind: bind9: Incorrect acceptance of NSEC3 records (CVE-2026-10723)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The Berkeley Internet Name Domain (BIND) is an implementation of the Domain Name System (DNS) protocols. BIND includes a DNS server (named); a resolver library (routines for applications to use when interfacing with DNS); and tools for verifying that the DNS server is operating correctly.

Security Fix(es):

• bind9: bind: Potential wildcard CNAME RPZ policy bypass (CVE-2026-11331)
• bind: bind9: DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field (CVE-2026-13321)
• bind: bind9: Potential memory usage beyond configured limits (CVE-2026-11622)
• bind: bind9: Cache poisoning via label count discrepancy, RRSIG, wildcards (CVE-2026-11721)
• bind: bind9: Unexpected exit with NSEC and NSEC3 both present (CVE-2026-13204)
• bind: bind9: Incorrect acceptance of NSEC3 records (CVE-2026-10723)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

BIND (Berkeley Internet Name Domain) is an implementation of the DNS (Domain Name System) protocols. BIND includes a DNS server (named), which resolves host names to IP addresses; a resolver library (routines for applications to use when interfacing with DNS); and tools for verifying that the DNS server is operating properly.

Security Fix(es):

• bind9: bind: Potential wildcard CNAME RPZ policy bypass (CVE-2026-11331)
• bind: bind9: DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field (CVE-2026-13321)
• bind: bind9: Potential memory usage beyond configured limits (CVE-2026-11622)
• bind: bind9: Cache poisoning via label count discrepancy, RRSIG, wildcards (CVE-2026-11721)
• bind: bind9: Unexpected exit with NSEC and NSEC3 both present (CVE-2026-13204)
• bind: bind9: Incorrect acceptance of NSEC3 records (CVE-2026-10723)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The BIND resolver accepts validly-signed NSEC records where the "Next Domain Name" field points outside the signer's zone. This issue affects BIND 9 versions 9.11.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.

• CVE-2026-10723: reject child-zone NSEC3 records whose signer does not match the owning zone apex, preventing forged authenticated NXDOMAIN responses
• CVE-2026-13321: reject signed NSEC records whose Next Domain Name points outside the signer's zone, preventing cross-zone DNSSEC cache poisoning

• CVE-2026-10723: reject child-zone NSEC3 records whose signer does not match the owning zone apex, preventing forged authenticated NXDOMAIN responses
• CVE-2026-13321: reject signed NSEC records whose Next Domain Name points outside the signer's zone, preventing cross-zone DNSSEC cache poisoning

• CVE-2026-10723: reject child-zone NSEC3 records whose signer does not match the owning zone apex, preventing forged authenticated NXDOMAIN responses
• CVE-2026-13321: reject signed NSEC records whose Next Domain Name points outside the signer's zone, preventing cross-zone DNSSEC cache poisoning

• CVE-2026-11331: return from RPZ wildcard CNAME expansion when the resulting name is too long instead of continuing with an invalid name
• CVE-2026-11721: reject RRSIG records whose Labels field is smaller than the signer's label count, and skip out-of-zone nodes in dnssec-signzone
• CVE-2026-13321: reject NSEC RRsets containing a record whose Next Domain Name points outside the signer's zone
• CVE-2026-10723: require the NSEC3 signer name to equal the zone apex derived from the NSEC3 owner name
• CVE-2026-13204: only accept an NSEC/NSEC3 denial record that has a matching RRSIG, and propagate the failure instead of asserting
• CVE-2026-11622: reference count cache RRset headers so superseded generations are reclaimed without waiting for the owning node to become unreferenced

• CVE-2026-13321: reject validly-signed NSEC records whose Next Domain Name points outside the signer's zone, preventing cross-zone DNSSEC cache poisoning

• CVE-2026-11331: return from RPZ wildcard CNAME expansion when the resulting name is too long instead of continuing with an invalid name
• CVE-2026-11721: reject RRSIG records whose Labels field is smaller than the signer's label count, and skip out-of-zone nodes in dnssec-signzone
• CVE-2026-13321: reject NSEC RRsets containing a record whose Next Domain Name points outside the signer's zone
• CVE-2026-10723: require the NSEC3 signer name to equal the zone apex derived from the NSEC3 owner name
• CVE-2026-13204: only accept an NSEC/NSEC3 denial record that has a matching RRSIG, and propagate the failure instead of asserting
• CVE-2026-11622: reference count cache RRset headers so superseded generations are reclaimed without waiting for the owning node to become unreferenced

• CVE-2026-13321: Reject NSEC records whose next owner name points outside the signer's zone, which let a signed zone forge proofs of non-existence for other zones
• CVE-2026-11622: Reference count the cache rdataset headers so a superseded generation is freed as soon as nothing holds it, instead of growing the node's down chain until the node itself becomes unreferenced

• SECURITY UPDATE: DNSSEC validation bypass via an out-of-zone NSEC Next Domain Name
  • debian/patches/CVE-2026-13321.patch: reject an NSEC RRset whose next owner name is not a subdomain of the RRSIG signer name in dns_dnssec_verify3() in lib/dns/dnssec.c.
  • CVE-2026-13321
• SECURITY UPDATE: assertion failure with dns64 and break-dnssec
  • debian/patches/CVE-2026-19666.patch: clear the noqname alias on the DNS64 filter64 path in query_find() in bin/named/query.c; add the upstream dns64 system test for a partially excluded wildcard AAAA.
  • CVE-2026-19666
• SECURITY UPDATE: crash on wildcard answers carrying both NSEC and NSEC3 proofs
  • debian/patches/CVE-2026-80274.patch: record the denial type the validator accepted and use it when caching and serving the NOQNAME proof in lib/dns/validator.c, lib/dns/resolver.c and lib/dns/rdatalist.c; adds dns_rdataset_addnoqnametype() so dns_rdataset_addnoqname() keeps its signature.
  • CVE-2026-80274
• Add root KSK-2024 (key tag 38696) trust anchor to bind.keys; fresh installs could not validate the root zone after the 2026-10-11 rollover
  • debian/patches/update_keys.patch: add the 38696 initial-key to bind.keys and the generated bind.keys.h next to the existing 20326 entry (upstream 609bf35075, carried as initial-key because 9.10 has no initial-ds).

• SECURITY UPDATE: DNSSEC validation bypass via an out-of-zone NSEC Next Domain Name
  • debian/patches/CVE-2026-13321.patch: reject an NSEC RRset whose next owner name is not a subdomain of the RRSIG signer name in dns_dnssec_verify3() in lib/dns/dnssec.c.
  • CVE-2026-13321
• SECURITY UPDATE: assertion failure with dns64 and break-dnssec
  • debian/patches/CVE-2026-19666.patch: clear the noqname alias on the DNS64 filter64 path in query_find() in bin/named/query.c.
  • CVE-2026-19666
• SECURITY UPDATE: crash on wildcard answers carrying both NSEC and NSEC3 proofs
  • debian/patches/CVE-2026-80274.patch: record the denial type the validator accepted and use it when caching and serving the NOQNAME proof in lib/dns/validator.c, lib/dns/resolver.c and lib/dns/rdatalist.c; adds dns_rdataset_addnoqnametype() so dns_rdataset_addnoqname() keeps its signature.
  • debian/libdns1100.symbols: add dns_rdataset_addnoqnametype.
  • CVE-2026-80274
• Add root KSK-2024 (key tag 38696) trust anchor to bind.keys; fresh installs could not validate the root zone after the 2026-10-11 rollover
  • debian/patches/update-root-ksk-38696.patch: add the 38696 initial-key to bind.keys and the generated bind.keys.h (upstream 609bf35075, carried as initial-key because 9.11 has no initial-ds).

• CVE-2026-13321: Reject NSEC records whose next owner name points outside the signer's zone, which let a signed zone forge proofs of non-existence for other zones
• CVE-2026-11622: Reference count the cache rdataset headers so a superseded generation is freed as soon as nothing holds it, instead of growing the node's down chain until the node itself becomes unreferenced

Updated bind packages fix security vulnerabilities: Incorrect acceptance of NSEC3 records. (CVE-2026-10723) Key Record using PRIVATEDNS algorithm may lead to unexpected exit. (CVE-2026-10822) Potential wildcard CNAME RPZ policy bypass. (CVE-2026-11331) Unnecessary validation of DNSSEC signed records. (CVE-2026-11605) Cache poisoning possible with label count discrepancy, RRSIG, and wildcards. (CVE-2026-11721) Record ordering based unexpected exit with CNAME or DNAME. (CVE-2026-12617) Unexpected exit in certain situations with NSEC and NSEC3 both present. (CVE-2026-13204) DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field. (CVE-2026-13321)

These are all security issues fixed in the bind-9.20.26-1.1 package on the GA media of openSUSE Tumbleweed.

This update for bind fixes the following issues

• Upgrade to release 9.20.26
• CVE-2026-10723: Incorrect acceptance of NSEC3 records (bsc#1271982).
• CVE-2026-10822: Key Record using PRIVATEDNS algorithm may lead to unexpected exit (bsc#1271983).
• CVE-2026-11331: Potential wildcard CNAME RPZ policy bypass (bsc#1271984).
• CVE-2026-11605: Unnecessary validation of DNSSEC signed records (bsc#1271985).
• CVE-2026-11622: Potential memory usage beyond configured limits (bsc#1271986).
• CVE-2026-11721: Cache poisoning possible with label count discrepancy, RRSIG, and wildcards (bsc#1271987).
• CVE-2026-12617: Record ordering based unexpected exit with CNAME or DNAME (bsc#1271988).
• CVE-2026-13204: Unexpected exit in certain situations with NSEC and NSEC3 both present (bsc#1271989).
• CVE-2026-13321: DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field (bsc#1271990).

This update for bind fixes the following issues:

Upgrade to release 9.20.26.

Security issues fixed:

• CVE-2026-10723: incorrect acceptance of NSEC3 records (bsc#1271982).
• CVE-2026-10822: key record using PRIVATEDNS algorithm may lead to unexpected exit (bsc#1271983).
• CVE-2026-11331: potential wildcard CNAME RPZ policy bypass (bsc#1271984).
• CVE-2026-11605: unnecessary validation of DNSSEC signed records (bsc#1271985).
• CVE-2026-11622: potential memory usage beyond configured limits (bsc#1271986).
• CVE-2026-11721: cache poisoning possible with label count discrepancy, RRSIG, and wildcards (bsc#1271987).
• CVE-2026-12617: record ordering based unexpected exit with CNAME or DNAME (bsc#1271988).
• CVE-2026-13204: unexpected exit in certain situations with NSEC and NSEC3 both present (bsc#1271989).
• CVE-2026-13321: DNSSEC validation bypass via out-of-zone NSEC Next field (bsc#1271990).

Other updates and bugfixes:

• Release 9.20.26:
  • Reclaim memory promptly when DNSSEC validations are canceled.
  • Removed Features:
    • Remove the secondary validator in query.c.
    • Remove ineffective TCP fallback after repeated UDP timeouts.
  • Feature Changes:
    • Fall back to TCP on receipt of a UDP response with a mismatched query ID.
    • Limit the number of glue records cached from a referral.
    • Fix a resolver stall on a CNAME response to a DS query.
  • Bug Fixes:
    • Fix a bug in DNS UPDATE processing with inline-signing enabled.
    • Properly detect private records before copying.
    • Tighten referral DS acceptance.
    • Don't synthesize negative responses with pending NSEC.
    • Check that an NSEC signer is at or above the name to be validated.
    • Don't evict DNSSEC-validated cache data on a CD=1 NXDOMAIN.
    • Fix a deny-answer-aliases configuration bypass issue.
    • Reject external referrals from forwarders.
    • Fix a zone transfer over TLS (XoT) issue when using the opportunistic TLS mode.
    • Unvalidated opt-out NSEC3 could be accepted in insecurity proof.
    • Check wildcard signer and NOQNAME signer match.
    • Fix CNAME resolution failure caused by a cached SERVFAIL response.
    • Reject unsupported RSA DNSKEY shapes during DNSSEC validation.
    • Fix a bug in GeoIP2 string matching.
    • Fix DNS-over-HTTPS (DoH) quota configuration issue.
    • Truncated reply to a TSIG query no longer stalls the resolver.
    • Ignore updates removing DNSKEY RRset with class ANY.
    • Ignore 0-byte reads in the TCP read callback.
    • Only print per-zone glue stats when zone-statistics is set to full.
    • CDS/CDNSKEY records were not removed when re-configuring the server.
    • Fix a crash when querying an empty non-terminal in a wildcard zone in RBTDB.
    • Stop reusing outgoing TCP connections the peer has already closed.
    • Fix DNSSEC validation failures for names under an apex DNAME.
      • The resolver now removes other RRsets at the same name when caching a CNAME.
    • Fix nxdomain-redirect combined with dns64.
    • Fix DNS64 owner case after DNAME restart.
    • Clear REDIRECT flag when it isn't needed.
    • Disable output escaping in bind9.xsl.
    • Fix crash on badly configured secondary signer.
    • Fix a possible crash on concurrent TKEY DELETE for the same key.
    • Reject RRSIG records covering meta-types.

This update for bind fixes the following issues:

• CVE-2026-10723: accepting incorrect child-zone NSEC3 records as valid can allow an attacker to forge authenticated NXDOMAIN responses for sibling zones (bsc#1271982).

• CVE-2026-10822: storing a DNS key record with an invalid PRIVATEDNS algorithm identifier length can trigger a consistency check failure (bsc#1271983).

• CVE-2026-11331: handling NAMETOOLONG error conditions incorrectly during RPZ wildcard CNAME processing can allow bypassing RPZ rules or triggering process exits (bsc#1271984).

• CVE-2026-11622: DNSSEC validating resolver under a random subdomain attack can suffer from runaway memory usage exceeding max-cache-size and affecting response rate (bsc#1271986).

• CVE-2026-11721: RRSIG with fewer labels than its containing zone when synth-from-dnssec is enabled can lead to wildcard generation (bsc#1271987).

• CVE-2026-12617: delayed or specific CNAME/DNAME query responses combined with positive A record responses can trigger an assertion failure (bsc#1271988).

• CVE-2026-13204: validating a domain covered by both NSEC and NSEC3 with an RRSIG for only one type can trigger an assertion failure (bsc#1271989).

• CVE-2026-13321: NSEC records with a Next Domain Name pointing outside the signer's zone can allow cross-zone cache poisoning and authenticated denial-of-service responses (bsc#1271990).

• Update to release 9.18.50:

• Remove ineffective TCP fallback after repeated UDP timeouts.
• Fall back to TCP on receipt of a UDP response with a mismatched query ID.
• Fix DNS64 owner case after DNAME restart.
• Clear REDIRECT flag when it isn't needed.

This update for bind fixes the following issues

• CVE-2026-10723: Incorrect acceptance of NSEC3 records (bsc#1271982).
• CVE-2026-11331: Potential wildcard CNAME RPZ policy bypass (bsc#1271984).
• CVE-2026-11622: Potential memory usage beyond configured limits (bsc#1271986).
• CVE-2026-11721: Cache poisoning possible with label count discrepancy, RRSIG, and wildcards (bsc#1271987).
• CVE-2026-13204: Unexpected exit in certain situations with NSEC and NSEC3 both present (bsc#1271989).
• CVE-2026-13321: DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field (bsc#1271990).

This update for bind fixes the following issues

• CVE-2026-10723: Incorrect acceptance of NSEC3 records (bsc#1271982).
• CVE-2026-11331: Potential wildcard CNAME RPZ policy bypass (bsc#1271984).
• CVE-2026-11622: Potential memory usage beyond configured limits (bsc#1271986).
• CVE-2026-11721: Cache poisoning possible with label count discrepancy, RRSIG, and wildcards (bsc#1271987).
• CVE-2026-13204: Unexpected exit in certain situations with NSEC and NSEC3 both present (bsc#1271989).
• CVE-2026-13321: DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field (bsc#1271990).

This update for bind fixes the following issues

• CVE-2026-11622: Potential memory usage beyond configured limits (bsc#1271986).
• CVE-2026-11721: Cache poisoning possible with label count discrepancy, RRSIG, and wildcards (bsc#1271987).
• CVE-2026-13204: Unexpected exit in certain situations with NSEC and NSEC3 both present (bsc#1271989).
• CVE-2026-13321: DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field (bsc#1271990).