| CVE-2026-97313 |
A recursive BIND server that receives a query with recursion desired (RD=1) followed by a non-recursive query (RD=0) may…
|
7.5
High
|
Oct 21, 2026 |
| CVE-2026-96888 |
A BIND resolver that is configured with both a "redirect" zone and "qname-minimization strict" may abort with an…
|
7.5
High
|
Oct 21, 2026 |
| CVE-2026-94300 |
Replaying GSS-TSIG signed UDP messages can result in memory corruption in "`named`"
|
8.1
High
|
Oct 21, 2026 |
| CVE-2026-19630 |
In a BIND resolver, inbound DNS protocol messages with a particular structure will result in additional processing, with…
|
7.5
High
|
Oct 21, 2026 |
| CVE-2026-77119 |
A validly signed NSEC3 from an unrelated sibling zone may be accepted as an insecurity proof, downgrading a secure…
|
5.9
Medium
|
Sep 16, 2026 |
| 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…
|
5.3
Medium
|
Sep 16, 2026 |
| CVE-2026-19668 |
A BIND recursive resolver may experience excessive resource consumption if it encounters large numbers of a particular…
|
5.3
Medium
|
Sep 16, 2026 |
| CVE-2026-19033 |
For a secondary zone with transfers restricted by TSIG, `named` may start to serve the data provided in a zone…
|
6.5
Medium
|
Sep 16, 2026 |
| CVE-2026-80274 |
If a BIND resolver sends a query for a DNSSEC-signed authoritative zone, and the authoritative server replies with a…
|
7.5
High
|
Sep 16, 2026 |
| CVE-2026-76163 |
If BIND is loaded with a "`named.conf`" file that contains no global "`options`" block, an attacker can send a query…
|
7.5
High
|
Sep 16, 2026 |
| CVE-2026-19666 |
On a resolver configured to use ``dns64``, if an applicable answer from the authoritative server is malformed in a…
|
7.5
High
|
Sep 16, 2026 |
| CVE-2026-81563 |
A BIND resolver encountering an SVCB/HTTPS AliasMode record referencing 14 or more SVCB/HTTPS ServiceMode records may…
|
7.5
High
|
Sep 16, 2026 |
| CVE-2026-78301 |
A malformed zone may contain an NS or DNAME node above its origin, which `named` treats as a zone cut
|
5.8
Medium
|
Sep 16, 2026 |
| CVE-2026-77692 |
An attacker can cause `named` to abort by sending a crafted DNS-over-HTTPS request with a cryptographically invalid…
|
7.5
High
|
Sep 16, 2026 |
| CVE-2026-19941 |
An inapplicable NSEC record may be accepted by a `named` resolver as proof that no wildcard exists, which could allow an…
|
5.9
Medium
|
Sep 16, 2026 |
| CVE-2026-19662 |
An attacker may be able to cause a `named` resolver to abort
|
5.9
Medium
|
Sep 16, 2026 |
| CVE-2026-19667 |
If an attacker-controlled authoritative server can produce a negative answer that is exactly 65536 bytes, then a flaw in…
|
7.5
High
|
Sep 16, 2026 |
| CVE-2026-81736 |
If a BIND resolver has cached a tree of SVCB/HTTPS AliasMode records, and is then queried for the root of that tree, the…
|
7.5
High
|
Sep 16, 2026 |
| CVE-2026-13321 |
The BIND resolver accepts validly-signed NSEC records where the "Next Domain Name" field points outside the signer's…
|
8.6
High
|
Jul 22, 2026 |
| CVE-2026-13204 |
If a provably insecure domain is covered by both an NSEC and NSEC3 record at the parent, and there exist an RRSIG for…
|
7.5
High
|
Jul 22, 2026 |
| CVE-2026-12617 |
The issue is unexpected program termination based on ordering and/or specific content in responses to queries for…
|
7.5
High
|
Jul 22, 2026 |
| CVE-2026-11721 |
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…
|
7.5
High
|
Jul 22, 2026 |
| CVE-2026-11622 |
A DNSSEC validating resolver that is under a random subdomain attack against a DNSSEC-signed zone can suffer from…
|
7.5
High
|
Jul 22, 2026 |
| CVE-2026-11605 |
The issue is a resource exhaustion vulnerability associated with DNSSEC validation
|
7.5
High
|
Jul 22, 2026 |
| CVE-2026-11331 |
An attacker who knows (or guesses) that a resolver uses RPZ with wildcard CNAME policies can craft query names long…
|
7.5
High
|
Jul 22, 2026 |