CVE-2026-75029

In a query response, an attacker may send "named" multiple copies of a record that should only exist once such as an SOA record. If the RDATA is the same on all the copies, the record is appended to the in-memory RDATA set, which can cause increased memory usage of the negative cache and possibly...

CVE-2026-75029 Message parser retains every identical singleton RDATA, enabling wire-to-work amplification

In a query response, an attacker may send named multiple copies of a record that should only exist once such as an SOA record. If the RDATA is the same on all the copies, the record is appended to the in-memory RDATA set, which can cause increased memory usage of the negative cache and possibly...

CVE-2026-75029

CVE-2026-75029 affects ISC BIND 9 (versions 9.11.0–9.18.50, 9.20.0–9.20.27, 9.21.0–9.21.25, and corresponding -S1 releases). The message parser fails to deduplicate singleton records (e.g., SOA) in a query response: when an attacker sends multiple copies with identical RDATA, each copy is appende...

CVE-2026-19668 Resource Exhaustion via Excessive DNSSEC Cryptographic Material Matching

A BIND recursive resolver may experience excessive resource consumption if it encounters large numbers of a particular kind of invalid DNSSEC record. Default limits on "max-records-per-type" and "max-types-per-name" help mitigate the exposure. This issue affects BIND 9 versions 9.11.0 through...

CVE-2026-19033

For a secondary zone with transfers restricted by TSIG, named may start to serve the data provided in a zone transfer before the final message with the TSIG signature arrives. This could allow an attacker that does not actually possess a valid TSIG signature to send unauthorized zone contents to ...

CVE-2026-19033 Unauthenticated IXFR deltas are applied to the live zone before TSIG verification

For a secondary zone with transfers restricted by TSIG, named may start to serve the data provided in a zone transfer before the final message with the TSIG signature arrives. This could allow an attacker that does not actually possess a valid TSIG signature to send unauthorized zone contents to ...

EUVD-2026-80781

For a secondary zone with transfers restricted by TSIG, named may start to serve the data provided in a zone transfer before the final message with the TSIG signature arrives. This could allow an attacker that does not actually possess a valid TSIG signature to send unauthorized zone contents to ...

CVE-2026-19033

BIND 9 named can serve zone data from a multi-message TCP IXFR transfer before the final TSIG signature arrives. If no valid signature ever arrives, the daemon does not roll back, allowing an unauthenticated attacker to inject unauthorized zone contents into a secondary server. Affected versions ...

CVE-2026-19033

For a secondary zone with transfers restricted by TSIG, "named" may start to serve the data provided in a zone transfer before the final message with the TSIG signature arrives. This could allow an attacker that does not actually possess a valid TSIG signature to send unauthorized zone contents t...

CVE-2026-19033 Unauthenticated IXFR deltas are applied to the live zone before TSIG verification

For a secondary zone with transfers restricted by TSIG, named may start to serve the data provided in a zone transfer before the final message with the TSIG signature arrives. This could allow an attacker that does not actually possess a valid TSIG signature to send unauthorized zone contents to ...

CVE-2026-80274 Validating resolver can abort while caching a mismatched NOQNAME proof

If a BIND resolver sends a query for a DNSSEC-signed authoritative zone, and the authoritative server replies with a valid wildcard answer and signed NSEC3 proof, followed by an unsigned NSEC at the same owner name, it will trigger an unexpected program exit. This issue affects BIND 9 versions...

CVE-2026-80274

BIND 9 validating resolvers are affected by a bug where the resolver can abort (unexpected program exit) while caching a mismatched NOQNAME proof . Specifically, when querying a DNSSEC-signed authoritative zone , a response containing a valid wildcard answer with a signed NSEC3 proof followed by ...

CVE-2026-80274 Validating resolver can abort while caching a mismatched NOQNAME proof

If a BIND resolver sends a query for a DNSSEC-signed authoritative zone, and the authoritative server replies with a valid wildcard answer and signed NSEC3 proof, followed by an unsigned NSEC at the same owner name, it will trigger an unexpected program exit. This issue affects BIND 9 versions...

CVE-2026-76163 named aborts on a TKEY query when the user configuration has no global options statement

If BIND is loaded with a "named.conf" file that contains no global "options" block, an attacker can send a query of QTYPE TKEY which may cause an assertion failure and subsequent unexpected program exit. This issue affects BIND 9 versions 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, and...

CVE-2026-76163 named aborts on a TKEY query when the user configuration has no global options statement

If BIND is loaded with a "named.conf" file that contains no global "options" block, an attacker can send a query of QTYPE TKEY which may cause an assertion failure and subsequent unexpected program exit. This issue affects BIND 9 versions 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, and...

CVE-2026-76163

ISC BIND 9 is vulnerable to a denial-of-service condition when the named process is loaded with a named.conf file that contains no global options block . In that configuration, an unauthenticated remote attacker can trigger an assertion failure by sending a single QTYPE TKEY query, causing an une...

EUVD-2026-80776

If BIND is loaded with a "named.conf" file that contains no global "options" block, an attacker can send a query of QTYPE TKEY which may cause an assertion failure and subsequent unexpected program exit. This issue affects BIND 9 versions 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, and...

CVE-2026-19666

On a resolver configured to use dns64, if an applicable answer from the authoritative server is malformed in a specific way, the resolver named process will exit unexpectedly. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1...

CVE-2026-19666

On a resolver configured to use "dns64", if an applicable answer from the authoritative server is malformed in a specific way, the resolver "named" process will exit unexpectedly. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1...

CVE-2026-19666 Use-after-free in query_addnoqnameproof() via the DNS64 filter64 path

On a resolver configured to use dns64, if an applicable answer from the authoritative server is malformed in a specific way, the resolver named process will exit unexpectedly. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1...