| CVE-2026-10822 |
If BIND encounters a particular invalid data structure in a DNS record, it will accept the invalid data, and may…
|
6.5
Medium
|
Jul 22, 2026 |
| CVE-2026-10723 |
BIND may accept incorrect child-zone NSEC3 records as valid, which could allow an attacker to forge authenticated…
|
6.8
Medium
|
Jul 22, 2026 |
| CVE-2026-5950 |
An unbounded resend loop vulnerability exists in the BIND 9 resolver state machine during bad-server handling,…
|
5.3
Medium
|
May 20, 2026 |
| CVE-2026-5947 |
Undefined behavior may result due to a race condition leading to a use-after-free violation
|
7.5
High
|
May 20, 2026 |
| CVE-2026-5946 |
Multiple flaws have been identified in `named` related to the handling of DNS messages whose CLASS is not Internet…
|
7.5
High
|
May 20, 2026 |
| CVE-2026-3593 |
A use-after-free vulnerability exists within the DNS-over-HTTPS implementation
|
7.4
High
|
May 20, 2026 |
| CVE-2026-3592 |
BIND resolvers are vulnerable to an amplified resource consumption/exhaustion attack
|
5.3
Medium
|
May 20, 2026 |
| CVE-2026-3039 |
BIND servers that are configured to use TKEY-based authentication via GSS-API tokens are vulnerable to excessive…
|
7.5
High
|
May 20, 2026 |
| CVE-2026-3591 |
A use-after-return vulnerability exists in the `named` server when handling DNS queries signed with SIG(0)
|
5.4
Medium
|
Mar 25, 2026 |
| CVE-2026-3119 |
Under certain conditions, `named` may crash when processing a correctly signed query containing a TKEY record
|
6.5
Medium
|
Mar 25, 2026 |
| CVE-2026-3104 |
A specially crafted domain can be used to cause a memory leak in a BIND resolver simply by querying this domain
|
7.5
High
|
Mar 25, 2026 |
| CVE-2026-1519 |
If a BIND resolver is performing DNSSEC validation and encounters a maliciously crafted zone, the resolver may consume…
|
7.5
High
|
Mar 25, 2026 |
| CVE-2025-13878 |
Malformed BRID/HHIT records can cause `named` to terminate unexpectedly
|
7.5
High
|
Jan 21, 2026 |
| CVE-2025-40780 |
In specific circumstances, due to a weakness in the Pseudo Random Number Generator (PRNG) that is used, it is possible…
|
8.6
High
|
Oct 22, 2025 |
| CVE-2025-40778 |
Under certain circumstances, BIND is too lenient when accepting records from answers, allowing an attacker to inject…
|
8.6
High
|
Oct 22, 2025 |
| CVE-2025-8677 |
Querying for records within a specially crafted zone containing certain malformed DNSKEY records can lead to CPU…
|
7.5
High
|
Oct 22, 2025 |
| CVE-2025-40777 |
If a `named` caching resolver is configured with `serve-stale-enable` `yes`, and with `stale-answer-client-timeout`…
|
7.5
High
|
Jul 16, 2025 |
| CVE-2025-40776 |
A `named` caching resolver that is configured to send ECS (EDNS Client Subnet) options may be vulnerable to a…
|
8.6
High
|
Jul 16, 2025 |
| CVE-2025-40775 |
When an incoming DNS protocol message includes a Transaction Signature (TSIG), BIND always checks it
|
7.5
High
|
May 21, 2025 |
| CVE-2024-12705 |
Clients using DNS-over-HTTPS (DoH) can exhaust a DNS resolver's CPU and/or memory by flooding it with crafted valid or…
|
7.5
High
|
Jan 29, 2025 |
| CVE-2024-11187 |
It is possible to construct a zone such that some queries to it will generate responses containing numerous records in…
|
7.5
High
|
Jan 29, 2025 |
| CVE-2024-4076 |
Client queries that trigger serving stale data and that also require lookups in local authoritative zone data may result…
|
7.5
High
|
Jul 23, 2024 |
| CVE-2024-1975 |
If a server hosts a zone containing a "KEY" Resource Record, or a resolver DNSSEC-validates a "KEY" Resource Record from…
|
7.5
High
|
Jul 23, 2024 |
| CVE-2024-1737 |
Resolver caches and authoritative zone databases that hold significant numbers of RRs for the same hostname (of any…
|
7.5
High
|
Jul 23, 2024 |
| CVE-2024-0760 |
A malicious client can send many DNS messages over TCP, potentially causing the server to become unstable while the…
|
7.5
High
|
Jul 23, 2024 |