IS
Vendor
ISC
298
CVEs
1
On KEV
4
New 30D
Products
BI9.8
BIND
ISC
184 CVEs1 on KEV0 new
B99.8
BIND 9
ISC
52 CVEs0 on KEV4 new
DH7.5
Dhcp
Isc
25 CVEs0 on KEV0 new
IN9.8
Inn
Isc
14 CVEs0 on KEV0 new
DH7.5
Dhcpd
Isc
8 CVEs0 on KEV0 new
KE7.5
Kea
ISC
6 CVEs0 on KEV0 new
ID7.5
ISC DHCP
ISC
4 CVEs0 on KEV0 new
DC–
Dhcp Client
Isc
2 CVEs0 on KEV0 new
DB–
Dnsco Bind
Isc
1 CVEs0 on KEV0 new
KD7.5
Kea DHCP
ISC
1 CVEs0 on KEV0 new
ST8.1
Stork
Isc
1 CVEs0 on KEV0 new
Recent CVEs
| CVE | Product | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2026-97313 | B9 BIND 9 ISC | 7.5 | Oct 21 | Specific RPZ configurations and query patterns may result in an unexpected exit |
| CVE-2026-96888 | B9 BIND 9 ISC | 7.5 | Oct 21 | Named may terminate unexpectedly when a redirect zone is used with strict QNAME minimization |
| CVE-2026-94300 | B9 BIND 9 ISC | 8.1 | Oct 21 | Concurrent GSS-TSIG messages corrupt memory |
| CVE-2026-19630 | B9 BIND 9 ISC | 7.5 | Oct 21 | Amplified resource exhaustion in inbound message processing |
| CVE-2026-77119 | B9 BIND 9 ISC | 5.9 | Sep 16 | NSEC3 insecure-referral proof can use unrelated cached NSEC3 RRsets |
| CVE-2026-75029 | B9 BIND 9 ISC | 5.3 | Sep 16 | Message parser retains every identical singleton RDATA, enabling wire-to-work amplification |
| CVE-2026-19668 | B9 BIND 9 ISC | 5.3 | Sep 16 | Resource Exhaustion via Excessive DNSSEC Cryptographic Material Matching |
| CVE-2026-19033 | B9 BIND 9 ISC | 6.5 | Sep 16 | Unauthenticated IXFR deltas are applied to the live zone before TSIG verification |
| CVE-2026-80274 | B9 BIND 9 ISC | 7.5 | Sep 16 | Validating resolver can abort while caching a mismatched NOQNAME proof |
| CVE-2026-76163 | B9 BIND 9 ISC | 7.5 | Sep 16 | named aborts on a TKEY query when the user configuration has no global options statement |
| CVE-2026-19666 | B9 BIND 9 ISC | 7.5 | Sep 16 | Use-after-free in query_addnoqnameproof() via the DNS64 filter64 path |
| CVE-2026-81563 | B9 BIND 9 ISC | 7.5 | Sep 16 | SVCB AliasMode additional-data error leaks qpcache references |
| CVE-2026-78301 | B9 BIND 9 ISC | 5.8 | Sep 16 | Out-of-zone database nodes can become authoritative zone cuts |
| CVE-2026-77692 | B9 BIND 9 ISC | 7.5 | Sep 16 | Unauthenticated remote crash of named via a single DoH SIG(0) request |
| CVE-2026-19941 | B9 BIND 9 ISC | 5.9 | Sep 16 | checkwildcard() accepts an out-of-zone NSEC as a wildcard-nonexistence proof |
| CVE-2026-19662 | B9 BIND 9 ISC | 5.9 | Sep 16 | qpcache NOQNAME proof use-after-free crashes recursive resolver |
| CVE-2026-19667 | B9 BIND 9 ISC | 7.5 | Sep 16 | Remote assertion failure via 16-bit length truncation in `dns_ncache_add()` |
| CVE-2026-81736 | B9 BIND 9 ISC | 7.5 | Sep 16 | Remote CPU denial of service through cached SVCB/HTTPS AliasMode trees |
| CVE-2026-13321 | B9 BIND 9 ISC | 8.6 | Jul 22 | DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field |
| CVE-2026-13204 | B9 BIND 9 ISC | 7.5 | Jul 22 | Unexpected exit in certain situations with NSEC and NSEC3 both present |
| CVE-2026-12617 | B9 BIND 9 ISC | 7.5 | Jul 22 | Record ordering based unexpected exit with CNAME or DNAME |
| CVE-2026-11721 | B9 BIND 9 ISC | 7.5 | Jul 22 | Cache poisoning possible with label count discrepancy, RRSIG, and wildcards |
| CVE-2026-11622 | B9 BIND 9 ISC | 7.5 | Jul 22 | Potential memory usage beyond configured limits |
| CVE-2026-11605 | B9 BIND 9 ISC | 7.5 | Jul 22 | Unnecessary validation of DNSSEC signed records |
| CVE-2026-11331 | B9 BIND 9 ISC | 7.5 | Jul 22 | Potential wildcard CNAME RPZ policy bypass |
| CVE-2026-10822 | B9 BIND 9 ISC | 6.5 | Jul 22 | Key Record using PRIVATEDNS algorithm may lead to unexpected exit |
| CVE-2026-10723 | B9 BIND 9 ISC | 6.8 | Jul 22 | Incorrect acceptance of NSEC3 records |
| CVE-2026-5950 | B9 BIND 9 ISC | 5.3 | May 20 | Unbounded resend loop in BIND 9 resolver |
| CVE-2026-5947 | B9 BIND 9 ISC | 5.9 | May 20 | SIG(0) validation during query flood may lead to undefined behavior |
| CVE-2026-5946 | B9 BIND 9 ISC | 7.5 | May 20 | Invalid handling of CLASS != IN |
| CVE-2026-3593 | B9 BIND 9 ISC | 9.8 | May 20 | Heap use-after-free vulnerability in BIND 9 DNS-over-HTTPS implementation |
| CVE-2026-3592 | B9 BIND 9 ISC | 5.3 | May 20 | Amplification vulnerabilities via self-pointed glue records |
| CVE-2026-3039 | B9 BIND 9 ISC | 7.5 | May 20 | BIND 9 server memory exhaustion during GSS-API TKEY negotiation |
| CVE-2026-3591 | B9 BIND 9 ISC | 5.4 | Mar 25 | A stack use-after-return flaw in SIG(0) handling code may enable ACL bypass |
| CVE-2026-3119 | B9 BIND 9 ISC | 6.5 | Mar 25 | Authenticated query containing a TKEY record may cause named to terminate unexpectedly |
| CVE-2026-3104 | B9 BIND 9 ISC | 7.5 | Mar 25 | Memory leak in code preparing DNSSEC proofs of non-existence |
| CVE-2026-1519 | B9 BIND 9 ISC | 7.5 | Mar 25 | Excessive NSEC3 iterations cause high CPU load during insecure delegation validation |
| CVE-2026-3608 | KE Kea ISC | 7.5 | Mar 25 | Stack overflow in Kea daemons |
| CVE-2025-40779 | KE Kea ISC | 7.5 | Aug 27 | Kea crash upon interaction between specific client options and subnet selection |
| CVE-2024-28872 | ST Stork Isc | 8.1 | Jul 11 | The TLS certificate validation code is flawed |
| CVE-2023-50868 | BI Bind Isc | 7.5 | Feb 14 | The Closest Encloser Proof aspect of the DNS protocol (in RFC 5155 when RFC 9276 guidance is skipped) allows remote attackers to cause a denial of service (CPU consumption for… |
| CVE-2023-50387 | BI Bind Isc | 7.5 | Feb 14 | Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of service (CPU consumption) via one or more… |
| CVE-2023-6516 | BI Bind Isc | 7.5 | Feb 13 | To keep its cache database efficient, `named` running as a recursive resolver occasionally attempts to clean up the database |
| CVE-2023-5680 | BI Bind Isc | 5.3 | Feb 13 | If a resolver cache has a very large number of ECS records stored for the same name, the process of cleaning the cache database node for this name can significantly impair query… |
| CVE-2023-5679 | BI Bind Isc | 7.5 | Feb 13 | A bad interaction between DNS64 and serve-stale may cause `named` to crash with an assertion failure during recursive resolution, when both of these features are enabled |
| CVE-2023-5517 | BI Bind Isc | 7.5 | Feb 13 | A flaw in query-handling code can cause `named` to exit prematurely with an assertion failure when: - `nxdomain-redirect <domain>;` is configured, and - the resolver receives… |
| CVE-2023-4408 | BI Bind Isc | 7.5 | Feb 13 | The DNS message parsing code in `named` includes a section whose computational complexity is overly high |
| CVE-2023-4236 | BI Bind Isc | 7.5 | Sep 20 | A flaw in the networking code handling DNS-over-TLS queries may cause `named` to terminate unexpectedly due to an assertion failure |
| CVE-2023-3341 | BI Bind Isc | 7.5 | Sep 20 | The code that processes control channel messages sent to `named` calls certain functions recursively during packet parsing |
| CVE-2023-2911 | BI Bind Isc | 7.5 | Jun 21 | If the `recursive-clients` quota is reached on a BIND 9 resolver configured with both `stale-answer-enable yes;` and `stale-answer-client-timeout 0;`, a sequence of… |
| CVE-2023-2829 | BI Bind Isc | 7.5 | Jun 21 | A `named` instance configured to run as a DNSSEC-validating recursive resolver with the Aggressive Use of DNSSEC-Validated Cache (RFC 8198) option (`synth-from-dnssec`) enabled… |
| CVE-2023-2828 | BI Bind Isc | 7.5 | Jun 21 | Every `named` instance configured to run as a recursive resolver maintains a cache database holding the responses to the queries it has recently sent to authoritative servers |
| CVE-2022-3924 | BI Bind Isc | 7.5 | Jan 26 | This issue can affect BIND 9 resolvers with `stale-answer-enable yes;` that also make use of the option `stale-answer-client-timeout`, configured with a value greater than zero |
| CVE-2022-3736 | BI Bind Isc | 7.5 | Jan 26 | BIND 9 resolver can crash when stale cache and stale answers are enabled, option `stale-answer-client-timeout` is set to a positive integer, and the resolver receives an RRSIG… |
| CVE-2022-3488 | BI Bind Isc | 7.5 | Jan 26 | Processing of repeated responses to the same query, where both responses contain ECS pseudo-options, but where the first is broken in some way, can cause BIND to exit with an… |
| CVE-2022-3094 | BI Bind Isc | 7.5 | Jan 26 | Sending a flood of dynamic DNS updates may cause `named` to allocate large amounts of memory |
| CVE-2022-2929 | ID ISC DHCP ISC | 6.5 | Oct 7 | DHCP memory leak |
| CVE-2022-2928 | ID ISC DHCP ISC | 6.5 | Oct 7 | An option refcount overflow exists in dhcpd |
| CVE-2022-3080 | BI Bind Isc | 7.5 | Sep 21 | By sending specific queries to the resolver, an attacker can cause named to crash |
| CVE-2022-38178 | BI Bind Isc | 7.5 | Sep 21 | By spoofing the target resolver with responses that have a malformed EdDSA signature, an attacker can trigger a small memory leak |