24h | 7d | 30d

Overview

  • ISC
  • BIND 9

16 Sep 2026
Published
16 Sep 2026
Updated

CVSS v3.1
MEDIUM (5.3)
EPSS
Pending

KEV

Description

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 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.

Statistics

  • 1 Post
  • 3 Interactions

Last activity: 2 hours ago

Overview

  • ISC
  • BIND 9

16 Sep 2026
Published
16 Sep 2026
Updated

CVSS v3.1
HIGH (7.5)
EPSS
Pending

KEV

Description

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 9.20.9-S1 through 9.20.27-S1.

Statistics

  • 1 Post
  • 3 Interactions

Last activity: 2 hours ago

Overview

  • ISC
  • BIND 9

16 Sep 2026
Published
16 Sep 2026
Updated

CVSS v3.1
HIGH (7.5)
EPSS
Pending

KEV

Description

An attacker can cause `named` to abort by sending a crafted DNS-over-HTTPS request with a cryptographically invalid SIG(0) record, and then closing the transport connection prematurely. This issue affects BIND 9 versions 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, and 9.20.9-S1 through 9.20.27-S1.

Statistics

  • 1 Post
  • 3 Interactions

Last activity: 2 hours ago

Overview

  • ISC
  • BIND 9

16 Sep 2026
Published
16 Sep 2026
Updated

CVSS v3.1
HIGH (7.5)
EPSS
Pending

KEV

Description

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 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 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.

Statistics

  • 1 Post
  • 3 Interactions

Last activity: 2 hours ago

Overview

  • ISC
  • BIND 9

16 Sep 2026
Published
16 Sep 2026
Updated

CVSS v3.1
HIGH (7.5)
EPSS
Pending

KEV

Description

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 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.

Statistics

  • 1 Post
  • 3 Interactions

Last activity: 2 hours ago

Overview

  • ISC
  • BIND 9

16 Sep 2026
Published
16 Sep 2026
Updated

CVSS v3.1
MEDIUM (5.8)
EPSS
Pending

KEV

Description

A malformed zone may contain an NS or DNAME node above its origin, which `named` treats as a zone cut. If an attacker inserts a malformed zone into a BIND authoritative server (e.g., via zone transfer), queries for names inside the configured zone then lose authoritative status and return an out-of-zone delegation. On a server that also provides recursion BIND can follow this locally sourced cut and cache attacker-supplied data, affecting names outside the configured zone. This situation persists as long as the malformed zone remains in the zone database. 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 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.

Statistics

  • 1 Post
  • 3 Interactions

Last activity: 2 hours ago

Overview

  • ISC
  • BIND 9

16 Sep 2026
Published
16 Sep 2026
Updated

CVSS v3.1
HIGH (7.5)
EPSS
Pending

KEV

Description

If an attacker-controlled authoritative server can produce a negative answer that is exactly 65536 bytes, then a flaw in `named` results in a negative cache entry of 0 bytes. When this entry is subsequently read, `named` aborts. 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 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.

Statistics

  • 1 Post
  • 3 Interactions

Last activity: 2 hours ago

Overview

  • ISC
  • BIND 9

16 Sep 2026
Published
16 Sep 2026
Updated

CVSS v3.1
HIGH (7.5)
EPSS
Pending

KEV

Description

If a BIND resolver has cached a tree of SVCB/HTTPS AliasMode records, and is then queried for the root of that tree, the resolver will spend disproportionate CPU time constructing the response. This issue affects BIND 9 versions 9.18.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.18.11-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.

Statistics

  • 1 Post
  • 3 Interactions

Last activity: 2 hours ago

Overview

  • ISC
  • BIND 9

16 Sep 2026
Published
16 Sep 2026
Updated

CVSS v3.1
MEDIUM (5.3)
EPSS
Pending

KEV

Description

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 lead to other memory attack vectors. 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 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.

Statistics

  • 1 Post
  • 3 Interactions

Last activity: 2 hours ago

Overview

  • ISC
  • BIND 9

16 Sep 2026
Published
16 Sep 2026
Updated

CVSS v3.1
MEDIUM (6.5)
EPSS
Pending

KEV

Description

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 a secondary server. Although no TSIG signature ever arrives, `named` does not rollback to the pre-transfer state. To exploit the vulnerability, the transfer must be a multi-message TCP IXFR, as described by RFC 8945. 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 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.

Statistics

  • 1 Post
  • 3 Interactions

Last activity: 2 hours ago
Showing 91 to 100 of 100 CVEs