<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="rss.xsl"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Internet Systems Consortium (ISC) — recent CVEs</title>
    <link>https://vulnogram.org/</link>
    <atom:link href="https://vulnogram.org/rss/isc" rel="self" type="application/rss+xml"/>
    <description>Most recent CVEs assigned by Internet Systems Consortium (ISC) (isc).</description>
    <image>
      <url>https://vulnogram.org/seaview/icons/isc.png</url>
      <title>Internet Systems Consortium (ISC) — recent CVEs</title>
      <link>https://vulnogram.org/</link>
    </image>
    <lastBuildDate>Wed, 21 Oct 2026 07:00:06 GMT</lastBuildDate>
    <item>
      <title>CVE-2026-77119 · 5.9 MEDIUM 🌩️ — NSEC3 insecure-referral proof can use unrelated cached NSEC3 RRsets</title>
      <link>https://vulnogram.org/CVE-2026-77119</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-77119</guid>
      <description>A validly signed NSEC3 from an unrelated sibling zone may be accepted as an insecurity proof, downgrading a secure delegation and letting a forged unsigned answer through. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20…</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 16 Sep 2026 14:17:11 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-75029 · 5.3 MEDIUM 🌩️ — Message parser retains every identical singleton RDATA, enabling wire-to-work amplification</title>
      <link>https://vulnogram.org/CVE-2026-75029</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-75029</guid>
      <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 increase…</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 16 Sep 2026 14:15:12 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-19668 · 5.3 MEDIUM 🌩️ — Resource Exhaustion via Excessive DNSSEC Cryptographic Material Matching</title>
      <link>https://vulnogram.org/CVE-2026-19668</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-19668</guid>
      <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 &quot;max-records-per-type&quot; and &quot;max-types-per-name&quot; help mitigate the exposure. This i…</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 16 Sep 2026 14:12:34 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-19033 · 6.5 MEDIUM 🌩️ — Unauthenticated IXFR deltas are applied to the live zone before TSIG verification</title>
      <link>https://vulnogram.org/CVE-2026-19033</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-19033</guid>
      <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…</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 16 Sep 2026 14:10:08 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-80274 · 7.5 HIGH 🌩️ — Validating resolver can abort while caching a mismatched NOQNAME proof</title>
      <link>https://vulnogram.org/CVE-2026-80274</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-80274</guid>
      <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 prog…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 16 Sep 2026 14:07:20 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-76163 · 7.5 HIGH 🌩️ — named aborts on a TKEY query when the user configuration has no global options statement</title>
      <link>https://vulnogram.org/CVE-2026-76163</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-76163</guid>
      <description>If BIND is loaded with a &quot;`named.conf`&quot; file that contains no global &quot;`options`&quot; 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…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 16 Sep 2026 14:05:34 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-19666 · 7.5 HIGH 🌩️ — Use-after-free in query_addnoqnameproof() via the DNS64 filter64 path</title>
      <link>https://vulnogram.org/CVE-2026-19666</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-19666</guid>
      <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 th…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 16 Sep 2026 14:02:30 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-81563 · 7.5 HIGH 🌩️ — SVCB AliasMode additional-data error leaks qpcache references</title>
      <link>https://vulnogram.org/CVE-2026-81563</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-81563</guid>
      <description>A BIND resolver encountering an SVCB/HTTPS AliasMode record referencing 14 or more SVCB/HTTPS ServiceMode records may fail to properly deallocate internal resources. If this happens repeatedly, resource exhaustion will eventually prevent the resolver…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 16 Sep 2026 14:00:04 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-78301 · 5.8 MEDIUM — Out-of-zone database nodes can become authoritative zone cuts</title>
      <link>https://vulnogram.org/CVE-2026-78301</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-78301</guid>
      <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 th…</description>
      <category>Medium</category>
      <pubDate>Wed, 16 Sep 2026 13:58:11 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-77692 · 7.5 HIGH 🌩️ — Unauthenticated remote crash of named via a single DoH SIG(0) request</title>
      <link>https://vulnogram.org/CVE-2026-77692</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-77692</guid>
      <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.…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 16 Sep 2026 13:55:45 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-19941 · 5.9 MEDIUM 🌩️ — checkwildcard() accepts an out-of-zone NSEC as a wildcard-nonexistence proof</title>
      <link>https://vulnogram.org/CVE-2026-19941</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-19941</guid>
      <description>An inapplicable NSEC record may be accepted by a `named` resolver as proof that no wildcard exists, which could allow an attacker at the same or an upstream level of the zone name to mask the existence of a victim&apos;s wildcard record. This issue affect…</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 16 Sep 2026 13:52:49 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-19662 · 5.9 MEDIUM 🌩️ — qpcache NOQNAME proof use-after-free crashes recursive resolver</title>
      <link>https://vulnogram.org/CVE-2026-19662</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-19662</guid>
      <description>An attacker may be able to cause a `named` resolver to abort. The attack requires inducing the victim resolver to send multiple queries for a DNSSEC-signed zone hosted by an authoritative server under the control of the attacker. If the auth responds…</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 16 Sep 2026 13:50:10 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-19667 · 7.5 HIGH 🌩️ — Remote assertion failure via 16-bit length truncation in `dns_ncache_add()`</title>
      <link>https://vulnogram.org/CVE-2026-19667</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-19667</guid>
      <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 BI…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 16 Sep 2026 13:46:56 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-81736 · 7.5 HIGH 🌩️ — Remote CPU denial of service through cached SVCB/HTTPS AliasMode trees</title>
      <link>https://vulnogram.org/CVE-2026-81736</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-81736</guid>
      <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.5…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 16 Sep 2026 13:44:28 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-13321 · 8.6 HIGH 🌩️ — DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field</title>
      <link>https://vulnogram.org/CVE-2026-13321</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-13321</guid>
      <description>The BIND resolver accepts validly-signed NSEC records where the &quot;Next Domain Name&quot; field points outside the signer&apos;s zone. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.11.3-S1 through 9.…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 22 Jul 2026 14:16:10 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-13204 · 7.5 HIGH 🌩️ — Unexpected exit in certain situations with NSEC and NSEC3 both present</title>
      <link>https://vulnogram.org/CVE-2026-13204</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-13204</guid>
      <description>If a provably insecure domain is covered by both an NSEC and NSEC3 record at the parent, and there exist an RRSIG for only one of these types, then BIND may exit unexpectedly with an assertion while validating this proof. This issue affects BIND 9 ve…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 22 Jul 2026 14:15:30 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-12617 · 7.5 HIGH 🌩️ — Record ordering based unexpected exit with CNAME or DNAME</title>
      <link>https://vulnogram.org/CVE-2026-12617</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-12617</guid>
      <description>The issue is unexpected program termination based on ordering and/or specific content in responses to queries for CNAME or DNAME, and A records. Specifically, if a client queries for a DNAME and A record below the DNAME to the resolver, and the autho…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 22 Jul 2026 14:14:46 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-11721 · 7.5 HIGH 🌩️ — Cache poisoning possible with label count discrepancy, RRSIG, and wildcards</title>
      <link>https://vulnogram.org/CVE-2026-11721</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-11721</guid>
      <description>It is possible for an attacker&apos;s zone to respond to a query with an RRSIG that has a smaller number of labels than the zone in which the RRSIG is contained. This causes `named` to produce a wildcard name for a zone that is shorter than the attacker&apos;s…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 22 Jul 2026 14:13:08 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-11622 · 7.5 HIGH 🌩️ — Potential memory usage beyond configured limits</title>
      <link>https://vulnogram.org/CVE-2026-11622</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-11622</guid>
      <description>A DNSSEC validating resolver that is under a random subdomain attack against a DNSSEC-signed zone can suffer from runaway memory usage. The attacker needs to be able to send queries faster than the resolver can perform validation. The increased memor…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 22 Jul 2026 14:12:19 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-11605 · 7.5 HIGH 🌩️ — Unnecessary validation of DNSSEC signed records</title>
      <link>https://vulnogram.org/CVE-2026-11605</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-11605</guid>
      <description>The issue is a resource exhaustion vulnerability associated with DNSSEC validation. BIND always validates all RRSIG records in an answer, even if they are not strictly needed. A query to an authoritative server/zone which returns many valid but super…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 22 Jul 2026 14:11:37 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-11331 · 7.5 HIGH 🌩️ — Potential wildcard CNAME RPZ policy bypass</title>
      <link>https://vulnogram.org/CVE-2026-11331</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-11331</guid>
      <description>An attacker who knows (or guesses) that a resolver uses RPZ with wildcard CNAME policies can craft query names long enough to trigger a NAMETOOLONG error condition during RPZ processing. This is not handled correctly and may lead to defeating the RPZ…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 22 Jul 2026 14:10:44 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-10822 · 6.5 MEDIUM 🌩️ — Key Record using PRIVATEDNS algorithm may lead to unexpected exit</title>
      <link>https://vulnogram.org/CVE-2026-10822</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-10822</guid>
      <description>If BIND encounters a particular invalid data structure in a DNS record, it will accept the invalid data, and may subsequently abort and exit. BIND will first need to store a DNS record for a key (KEY, DNSKEY, etc.). That key must specify a PRIVATEDNS…</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 22 Jul 2026 14:09:57 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-10723 · 6.8 MEDIUM 🌩️ — Incorrect acceptance of NSEC3 records</title>
      <link>https://vulnogram.org/CVE-2026-10723</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-10723</guid>
      <description>BIND may accept incorrect child-zone NSEC3 records as valid, which could allow an attacker to forge authenticated NXDOMAIN responses. This issue affects BIND 9 versions 9.18.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.11.3-S1…</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 22 Jul 2026 14:08:19 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-5950 · 5.3 MEDIUM 🌩️ — Unbounded resend loop in BIND 9 resolver</title>
      <link>https://vulnogram.org/CVE-2026-5950</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-5950</guid>
      <description>An unbounded resend loop vulnerability exists in the BIND 9 resolver state machine during bad-server handling, enabling a remote unauthenticated attacker to cause severe resource exhaustion by sending queries that trigger specific retry conditions. T…</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 20 May 2026 13:10:19 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-5947 · 7.5 HIGH 🌩️ — SIG(0) validation during query flood may lead to undefined behavior</title>
      <link>https://vulnogram.org/CVE-2026-5947</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-5947</guid>
      <description>Undefined behavior may result due to a race condition leading to a use-after-free violation. If BIND receives an incoming DNS message signed with SIG(0), it begins work to validate that signature. If, during that validation, the &quot;recursive-clients&quot; l…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 20 May 2026 13:10:11 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-5946 · 7.5 HIGH 🌩️ — Invalid handling of CLASS != IN</title>
      <link>https://vulnogram.org/CVE-2026-5946</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-5946</guid>
      <description>Multiple flaws have been identified in `named` related to the handling of DNS messages whose CLASS is not Internet (`IN`) — for example, `CHAOS` or `HESIOD`, or DNS messages that specify meta-classes (`ANY` or `NONE`) in the question section. Special…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 20 May 2026 13:10:03 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-3593 · 7.4 HIGH 🌩️ — Heap use-after-free vulnerability in BIND 9 DNS-over-HTTPS implementation</title>
      <link>https://vulnogram.org/CVE-2026-3593</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-3593</guid>
      <description>A use-after-free vulnerability exists within the DNS-over-HTTPS implementation. This issue affects BIND 9 versions 9.20.0 through 9.20.22, 9.21.0 through 9.21.21, and 9.20.9-S1 through 9.20.22-S1. BIND 9 versions 9.18.0 through 9.18.48 and 9.18.11-S1…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 20 May 2026 13:09:47 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-3592 · 5.3 MEDIUM 🌩️ — Amplification vulnerabilities via self-pointed glue records</title>
      <link>https://vulnogram.org/CVE-2026-3592</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-3592</guid>
      <description>BIND resolvers are vulnerable to an amplified resource consumption/exhaustion attack. If a victim resolver makes a query to a specially crafted zone, the resolver will consume disproportionate resources. This issue affects BIND 9 versions 9.11.0 thro…</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 20 May 2026 13:09:21 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-3039 · 7.5 HIGH 🌩️ — BIND 9 server memory exhaustion during GSS-API TKEY negotiation</title>
      <link>https://vulnogram.org/CVE-2026-3039</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-3039</guid>
      <description>BIND servers that are configured to use TKEY-based authentication via GSS-API tokens are vulnerable to excessive memory consumption when receiving and processing maliciously-constructed packets. Typically these servers will be found in Active Directo…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 20 May 2026 13:09:04 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-3591 · 5.4 MEDIUM — A stack use-after-return flaw in SIG(0) handling code may enable ACL bypass</title>
      <link>https://vulnogram.org/CVE-2026-3591</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-3591</guid>
      <description>A use-after-return vulnerability exists in the `named` server when handling DNS queries signed with SIG(0). Using a specially-crafted DNS request, an attacker may be able to cause an ACL to improperly (mis)match an IP address. In a default-allow ACL…</description>
      <category>Medium</category>
      <pubDate>Wed, 25 Mar 2026 13:34:14 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-3119 · 6.5 MEDIUM — Authenticated query containing a TKEY record may cause named to terminate unexpectedly</title>
      <link>https://vulnogram.org/CVE-2026-3119</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-3119</guid>
      <description>Under certain conditions, `named` may crash when processing a correctly signed query containing a TKEY record. The affected code can only be reached if an incoming request has a valid transaction signature (TSIG) from a key declared in the `named` co…</description>
      <category>Medium</category>
      <pubDate>Wed, 25 Mar 2026 13:31:54 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-3104 · 7.5 HIGH 🌩️ — Memory leak in code preparing DNSSEC proofs of non-existence</title>
      <link>https://vulnogram.org/CVE-2026-3104</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-3104</guid>
      <description>A specially crafted domain can be used to cause a memory leak in a BIND resolver simply by querying this domain. This issue affects BIND 9 versions 9.20.0 through 9.20.20, 9.21.0 through 9.21.19, and 9.20.9-S1 through 9.20.20-S1. BIND 9 versions 9.18…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 25 Mar 2026 13:29:19 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-1519 · 7.5 HIGH 🌩️ — Excessive NSEC3 iterations cause high CPU load during insecure delegation validation</title>
      <link>https://vulnogram.org/CVE-2026-1519</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-1519</guid>
      <description>If a BIND resolver is performing DNSSEC validation and encounters a maliciously crafted zone, the resolver may consume excessive CPU. Authoritative-only servers are generally unaffected, although there are circumstances where authoritative servers ma…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 25 Mar 2026 13:25:19 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-3608 · 7.5 HIGH 🌩️ — Stack overflow in Kea daemons</title>
      <link>https://vulnogram.org/CVE-2026-3608</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-3608</guid>
      <description>Sending a maliciously crafted message to the kea-ctrl-agent, kea-dhcp-ddns, kea-dhcp4, or kea-dhcp6 daemons over any configured API socket or HA listener can cause the receiving daemon to exit with a stack overflow error. This issue affects Kea versi…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 25 Mar 2026 08:46:48 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2025-13878 · 7.5 HIGH 🌩️ — Malformed BRID/HHIT records can cause named to terminate unexpectedly</title>
      <link>https://vulnogram.org/CVE-2025-13878</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2025-13878</guid>
      <description>Malformed BRID/HHIT records can cause `named` to terminate unexpectedly. This issue affects BIND 9 versions 9.18.40 through 9.18.43, 9.20.13 through 9.20.17, 9.21.12 through 9.21.16, 9.18.40-S1 through 9.18.43-S1, and 9.20.13-S1 through 9.20.17-S1.</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 21 Jan 2026 14:43:27 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2025-11232 · 7.5 HIGH 🌩️ — Invalid characters cause assert</title>
      <link>https://vulnogram.org/CVE-2025-11232</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2025-11232</guid>
      <description>To trigger the issue, three configuration parameters must have specific settings: &quot;hostname-char-set&quot; must be left at the default setting, which is &quot;[^A-Za-z0-9.-]&quot;; &quot;hostname-char-replacement&quot; must be empty (the default); and &quot;ddns-qualifying-suffix…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 29 Oct 2025 18:02:39 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2025-40780 · 8.6 HIGH 🌩️ — Cache poisoning due to weak PRNG</title>
      <link>https://vulnogram.org/CVE-2025-40780</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2025-40780</guid>
      <description>In specific circumstances, due to a weakness in the Pseudo Random Number Generator (PRNG) that is used, it is possible for an attacker to predict the source port and query ID that BIND will use. This issue affects BIND 9 versions 9.16.0 through 9.16.…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 22 Oct 2025 15:48:27 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2025-40778 · 8.6 HIGH 🌩️ — Cache poisoning attacks with unsolicited RRs</title>
      <link>https://vulnogram.org/CVE-2025-40778</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2025-40778</guid>
      <description>Under certain circumstances, BIND is too lenient when accepting records from answers, allowing an attacker to inject forged data into the cache. This issue affects BIND 9 versions 9.11.0 through 9.16.50, 9.18.0 through 9.18.39, 9.20.0 through 9.20.13…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 22 Oct 2025 15:47:13 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2025-8677 · 7.5 HIGH 🌩️ — Resource exhaustion via malformed DNSKEY handling</title>
      <link>https://vulnogram.org/CVE-2025-8677</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2025-8677</guid>
      <description>Querying for records within a specially crafted zone containing certain malformed DNSKEY records can lead to CPU exhaustion. This issue affects BIND 9 versions 9.18.0 through 9.18.39, 9.20.0 through 9.20.13, 9.21.0 through 9.21.12, 9.18.11-S1 through…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 22 Oct 2025 15:43:10 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2025-8696 · 7.5 HIGH 🌩️ — DoS attack against the Stork UI from an unauthenticated user</title>
      <link>https://vulnogram.org/CVE-2025-8696</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2025-8696</guid>
      <description>If an unauthenticated user sends a large amount of data to the Stork UI, it may cause memory and disk use problems for the system running the Stork server. This issue affects Stork versions 1.0.0 through 2.3.0.</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 10 Sep 2025 17:59:52 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2025-40779 · 7.5 HIGH 🌩️ — Kea crash upon interaction between specific client options and subnet selection</title>
      <link>https://vulnogram.org/CVE-2025-40779</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2025-40779</guid>
      <description>If a DHCPv4 client sends a request with some specific options, and Kea fails to find an appropriate subnet for the client, the `kea-dhcp4` process will abort with an assertion failure. This happens only if the client request is unicast directly to Ke…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 27 Aug 2025 20:23:29 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2025-40777 · 7.5 HIGH 🌩️ — A possible assertion failure when &apos;stale-answer-client-timeout&apos; is set to &apos;0&apos;</title>
      <link>https://vulnogram.org/CVE-2025-40777</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2025-40777</guid>
      <description>If a `named` caching resolver is configured with `serve-stale-enable` `yes`, and with `stale-answer-client-timeout` set to `0` (the only allowable value other than `disabled`), and if the resolver, in the process of resolving a query, encounters a CN…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 16 Jul 2025 17:38:06 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2025-40776 · 8.6 HIGH 🌩️ — Birthday Attack against Resolvers supporting ECS</title>
      <link>https://vulnogram.org/CVE-2025-40776</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2025-40776</guid>
      <description>A `named` caching resolver that is configured to send ECS (EDNS Client Subnet) options may be vulnerable to a cache-poisoning attack. This issue affects BIND 9 versions 9.11.3-S1 through 9.16.50-S1, 9.18.11-S1 through 9.18.37-S1, and 9.20.9-S1 throug…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 16 Jul 2025 13:41:01 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2025-32803 · 4 MEDIUM — Insecure file permissions can result in confidential information leakage</title>
      <link>https://vulnogram.org/CVE-2025-32803</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2025-32803</guid>
      <description>In some cases, Kea log files or lease files may be world-readable. This issue affects Kea versions 2.4.0 through 2.4.1, 2.6.0 through 2.6.2, and 2.7.0 through 2.7.8.</description>
      <category>Medium</category>
      <pubDate>Wed, 28 May 2025 17:08:20 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2025-32802 · 6.1 MEDIUM — Insecure handling of file paths allows multiple local attacks</title>
      <link>https://vulnogram.org/CVE-2025-32802</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2025-32802</guid>
      <description>Kea configuration and API directives can be used to overwrite arbitrary files, subject to permissions granted to Kea. Many common configurations run Kea as root, leave the API entry points unsecured by default, and/or place the control sockets in ins…</description>
      <category>Medium</category>
      <pubDate>Wed, 28 May 2025 17:08:11 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2025-32801 · 7.8 HIGH — Loading a malicious hook library can lead to local privilege escalation</title>
      <link>https://vulnogram.org/CVE-2025-32801</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2025-32801</guid>
      <description>Kea configuration and API directives can be used to load a malicious hook library. Many common configurations run Kea as root, leave the API entry points unsecured by default, and/or place the control sockets in insecure paths. This issue affects Kea…</description>
      <category>High</category>
      <pubDate>Wed, 28 May 2025 17:03:34 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2025-40775 · 7.5 HIGH 🌩️ — DNS message with invalid TSIG causes an assertion failure</title>
      <link>https://vulnogram.org/CVE-2025-40775</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2025-40775</guid>
      <description>When an incoming DNS protocol message includes a Transaction Signature (TSIG), BIND always checks it. If the TSIG contains an invalid value in the algorithm field, BIND immediately aborts with an assertion failure. This issue affects BIND 9 versions…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 21 May 2025 12:35:01 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2024-12705 · 7.5 HIGH 🌩️ — DNS-over-HTTPS implementation suffers from multiple issues under heavy query load</title>
      <link>https://vulnogram.org/CVE-2024-12705</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2024-12705</guid>
      <description>Clients using DNS-over-HTTPS (DoH) can exhaust a DNS resolver&apos;s CPU and/or memory by flooding it with crafted valid or invalid HTTP/2 traffic. This issue affects BIND 9 versions 9.18.0 through 9.18.32, 9.20.0 through 9.20.4, 9.21.0 through 9.21.3, an…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 29 Jan 2025 21:40:27 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2024-11187 · 7.5 HIGH 🌩️ — Many records in the additional section cause CPU exhaustion</title>
      <link>https://vulnogram.org/CVE-2024-11187</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2024-11187</guid>
      <description>It is possible to construct a zone such that some queries to it will generate responses containing numerous records in the Additional section. An attacker sending many such queries can cause either the authoritative server itself or an independent re…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 29 Jan 2025 21:40:11 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2024-4076 · 7.5 HIGH 🌩️ — Assertion failure when serving both stale cache data and authoritative zone content</title>
      <link>https://vulnogram.org/CVE-2024-4076</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2024-4076</guid>
      <description>Client queries that trigger serving stale data and that also require lookups in local authoritative zone data may result in an assertion failure. This issue affects BIND 9 versions 9.16.13 through 9.16.50, 9.18.0 through 9.18.27, 9.19.0 through 9.19.…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Tue, 23 Jul 2024 14:40:57 GMT</pubDate>
    </item>
  </channel>
</rss>
