https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 11:11:14 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-369386 EUVD-2026-369386 https://cve.radiocsirt.org/vuln/euvd-2026-369386 https://cve.radiocsirt.org/vuln/fkie_cve-2026-55991 <p>In NLnet Labs Unbound 1.22.0 up to and including 1.25.1, a remote unauthenticated client can trigger a libngtcp2 assertion (if compiled with assertions on) and terminate the entire Unbound process using a single DNS-over-QUIC (DoQ) connection and one normal DNS query. This is caused by an erroneous error value passed to libngtcp2. When &#39;ngtcp2_conn_writev_stream()&#39; returns &#39;NGTCP2_ERR_STREAM_DATA_BLOCKED&#39;, Unbound continues to call &#39;ngtcp2_ccerr_set_application_error()&#39; with a &#39;-1&#39; error value. The &#39;int&#39; literal &#39;-1&#39; is implicitly converted to the function&#39;s &#39;uint64_t error_code&#39; parameter as &#39;0xFFFFFFFFFFFFFFFF&#39;. The follow-on &#39;ngtcp2_conn_write_connection_close()&#39; serialises that value as a QUIC variable-length integer; because &#39;2^64-1&#39; exceeds the 62-bit varint ceiling, &#39;ngtcp2_put_uvarintlen()&#39; fails &#39;assert(n &lt; 4611686018427387904ULL)&#39; and the whole resolver process aborts. A remote, unauthenticated DoQ client can trigger this deterministically with a single QUIC connection by advertising &#39;initial_max_stream_data_bidi_local = 1&#39; in its transport parameters and sending one DoQ query without ever reading the stream.</p> <p>In NLnet Labs Unbound 1.22.0 up to and including 1.25.1, a remote unauthenticated client can trigger a libngtcp2 assertion (if compiled with assertions on) and terminate the entire Unbound process using a single DNS-over-QUIC (DoQ) connection and one normal DNS query. This is caused by an erroneous error value passed to libngtcp2. When &#39;ngtcp2_conn_writev_stream()&#39; returns &#39;NGTCP2_ERR_STREAM_DATA_BLOCKED&#39;, Unbound continues to call &#39;ngtcp2_ccerr_set_application_error()&#39; with a &#39;-1&#39; error value. The &#39;int&#39; literal &#39;-1&#39; is implicitly converted to the function&#39;s &#39;uint64_t error_code&#39; parameter as &#39;0xFFFFFFFFFFFFFFFF&#39;. The follow-on &#39;ngtcp2_conn_write_connection_close()&#39; serialises that value as a QUIC variable-length integer; because &#39;2^64-1&#39; exceeds the 62-bit varint ceiling, &#39;ngtcp2_put_uvarintlen()&#39; fails &#39;assert(n &lt; 4611686018427387904ULL)&#39; and the whole resolver process aborts. A remote, unauthenticated DoQ client can trigger this deterministically with a single QUIC connection by advertising &#39;initial_max_stream_data_bidi_local = 1&#39; in its transport parameters and sending one DoQ query without ever reading the stream.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-55991 https://cve.radiocsirt.org/vuln/ghsa-j6hj-wvx2-8wqp <p>In NLnet Labs Unbound 1.22.0 up to and including 1.25.1, a remote unauthenticated client can trigger a libngtcp2 assertion (if compiled with assertions on) and terminate the entire Unbound process using a single DNS-over-QUIC (DoQ) connection and one normal DNS query. This is caused by an erroneous error value passed to libngtcp2. When &#39;ngtcp2_conn_writev_stream()&#39; returns &#39;NGTCP2_ERR_STREAM_DATA_BLOCKED&#39;, Unbound continues to call &#39;ngtcp2_ccerr_set_application_error()&#39; with a &#39;-1&#39; error value. The &#39;int&#39; literal &#39;-1&#39; is implicitly converted to the function&#39;s &#39;uint64_t error_code&#39; parameter as &#39;0xFFFFFFFFFFFFFFFF&#39;. The follow-on &#39;ngtcp2_conn_write_connection_close()&#39; serialises that value as a QUIC variable-length integer; because &#39;2^64-1&#39; exceeds the 62-bit varint ceiling, &#39;ngtcp2_put_uvarintlen()&#39; fails &#39;assert(n &lt; 4611686018427387904ULL)&#39; and the whole resolver process aborts. A remote, unauthenticated DoQ client can trigger this deterministically with a single QUIC connection by advertising &#39;initial_max_stream_data_bidi_local = 1&#39; in its transport parameters and sending one DoQ query without ever reading the stream.</p> <p>In NLnet Labs Unbound 1.22.0 up to and including 1.25.1, a remote unauthenticated client can trigger a libngtcp2 assertion (if compiled with assertions on) and terminate the entire Unbound process using a single DNS-over-QUIC (DoQ) connection and one normal DNS query. This is caused by an erroneous error value passed to libngtcp2. When &#39;ngtcp2_conn_writev_stream()&#39; returns &#39;NGTCP2_ERR_STREAM_DATA_BLOCKED&#39;, Unbound continues to call &#39;ngtcp2_ccerr_set_application_error()&#39; with a &#39;-1&#39; error value. The &#39;int&#39; literal &#39;-1&#39; is implicitly converted to the function&#39;s &#39;uint64_t error_code&#39; parameter as &#39;0xFFFFFFFFFFFFFFFF&#39;. The follow-on &#39;ngtcp2_conn_write_connection_close()&#39; serialises that value as a QUIC variable-length integer; because &#39;2^64-1&#39; exceeds the 62-bit varint ceiling, &#39;ngtcp2_put_uvarintlen()&#39; fails &#39;assert(n &lt; 4611686018427387904ULL)&#39; and the whole resolver process aborts. A remote, unauthenticated DoQ client can trigger this deterministically with a single QUIC connection by advertising &#39;initial_max_stream_data_bidi_local = 1&#39; in its transport parameters and sending one DoQ query without ever reading the stream.</p> https://cve.radiocsirt.org/vuln/ghsa-j6hj-wvx2-8wqp https://cve.radiocsirt.org/vuln/msrc_cve-2026-55991 msrc_CVE-2026-55991 https://cve.radiocsirt.org/vuln/msrc_cve-2026-55991 https://cve.radiocsirt.org/vuln/opensuse-su-2026:11380-1 <p>libunbound8-1.25.2-1.1 on GA media</p> <p>libunbound8-1.25.2-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:11380-1 https://cve.radiocsirt.org/vuln/rhsa-2026:43588 <p>unbound: Unbound: Denial of Service via assertion failure in DNS-over-QUIC environments unbound: Unbound: Denial of Service via improper validation of DNS-over-QUIC client length unbound: Unbound: Denial of Service via crafted DNSCrypt query unbound: Unbound: Denial of Service via terminated DNS-over-QUIC queries unbound: Unbound: DNS cache integrity issue unbound: Unbound: Denial of Service due to &#39;harden-below-nxdomain&#39; logic bypass unbound: Unbound: Cache poisoning via insufficient RRSIG.Labels validation and premature cache writes unbound: Unbound: Information disclosure via DNSSEC wildcard replay unbound: Unbound: Denial of Service via DNSSEC query amplification bypass unbound: Unbound: Denial of Service due to freed pointer dereference in DNS-over-TLS handling unbound: Unbound: Insecure DNS redirection via spoofed DNS answers unbound: Unbound: DNS response policy replacement via hostname spoofing unbound: NLnet Labs Unbound: Denial of Service via crafted DNS glue records unbound: Unbound: DNS cache poisoning via UDP source port predictability unbound: Unbound: Denial of service due to memory corruption under specific configurations. unbound: Unbound: DNS Cookie security bypass via incorrect server cookie calculation unbound: Unbound: Information disclosure due to local policy bypass via unbound-control unbound: Unbound: Denial of Service via crafted DNS responses with expired records unbound: Unbound: Denial of Service via malformed EDNS Report-Channel option unbound:…</p> <p>unbound: Unbound: Denial of Service via assertion failure in DNS-over-QUIC environments unbound: Unbound: Denial of Service via improper validation of DNS-over-QUIC client length unbound: Unbound: Denial of Service via crafted DNSCrypt query unbound: Unbound: Denial of Service via terminated DNS-over-QUIC queries unbound: Unbound: DNS cache integrity issue unbound: Unbound: Denial of Service due to &#39;harden-below-nxdomain&#39; logic bypass unbound: Unbound: Cache poisoning via insufficient RRSIG.Labels validation and premature cache writes unbound: Unbound: Information disclosure via DNSSEC wildcard replay unbound: Unbound: Denial of Service via DNSSEC query amplification bypass unbound: Unbound: Denial of Service due to freed pointer dereference in DNS-over-TLS handling unbound: Unbound: Insecure DNS redirection via spoofed DNS answers unbound: Unbound: DNS response policy replacement via hostname spoofing unbound: NLnet Labs Unbound: Denial of Service via crafted DNS glue records unbound: Unbound: DNS cache poisoning via UDP source port predictability unbound: Unbound: Denial of service due to memory corruption under specific configurations. unbound: Unbound: DNS Cookie security bypass via incorrect server cookie calculation unbound: Unbound: Information disclosure due to local policy bypass via unbound-control unbound: Unbound: Denial of Service via crafted DNS responses with expired records unbound: Unbound: Denial of Service via malformed EDNS Report-Channel option unbound:…</p> https://cve.radiocsirt.org/vuln/rhsa-2026:43588 https://cve.radiocsirt.org/vuln/suse-su-2026:23050-1 <p>Security update for unbound</p> <p>Security update for unbound</p> https://cve.radiocsirt.org/vuln/suse-su-2026:23050-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-55991 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: unbound, Ubuntu:Pro:16.04:LTS: unbound, Ubuntu:Pro:18.04:LTS: unbound, Ubuntu:Pro:20.04:LTS: unbound, Ubuntu:22.04:LTS: unbound, Ubuntu:24.04:LTS: unbound, Ubuntu:26.04:LTS: unbound</p> <p>In NLnet Labs Unbound 1.22.0 up to and including 1.25.1, a remote unauthenticated client can trigger a libngtcp2 assertion (if compiled with assertions on) and terminate the entire Unbound process using a single DNS-over-QUIC (DoQ) connection and one normal DNS query. This is caused by an erroneous error value passed to libngtcp2. When &#39;ngtcp2_conn_writev_stream()&#39; returns &#39;NGTCP2_ERR_STREAM_DATA_BLOCKED&#39;, Unbound continues to call &#39;ngtcp2_ccerr_set_application_error()&#39; with a &#39;-1&#39; error value. The &#39;int&#39; literal &#39;-1&#39; is implicitly converted to the function&#39;s &#39;uint64_t error_code&#39; parameter as &#39;0xFFFFFFFFFFFFFFFF&#39;. The follow-on &#39;ngtcp2_conn_write_connection_close()&#39; serialises that value as a QUIC variable-length integer; because &#39;2^64-1&#39; exceeds the 62-bit varint ceiling, &#39;ngtcp2_put_uvarintlen()&#39; fails &#39;assert(n &lt; 4611686018427387904ULL)&#39; and the whole resolver process aborts. A remote, unauthenticated DoQ client can trigger this deterministically with a single QUIC connection by advertising &#39;initial_max_stream_data_bidi_local = 1&#39; in its transport parameters and sending one DoQ query without ever reading the stream.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: unbound, Ubuntu:Pro:16.04:LTS: unbound, Ubuntu:Pro:18.04:LTS: unbound, Ubuntu:Pro:20.04:LTS: unbound, Ubuntu:22.04:LTS: unbound, Ubuntu:24.04:LTS: unbound, Ubuntu:26.04:LTS: unbound</p> <p>In NLnet Labs Unbound 1.22.0 up to and including 1.25.1, a remote unauthenticated client can trigger a libngtcp2 assertion (if compiled with assertions on) and terminate the entire Unbound process using a single DNS-over-QUIC (DoQ) connection and one normal DNS query. This is caused by an erroneous error value passed to libngtcp2. When &#39;ngtcp2_conn_writev_stream()&#39; returns &#39;NGTCP2_ERR_STREAM_DATA_BLOCKED&#39;, Unbound continues to call &#39;ngtcp2_ccerr_set_application_error()&#39; with a &#39;-1&#39; error value. The &#39;int&#39; literal &#39;-1&#39; is implicitly converted to the function&#39;s &#39;uint64_t error_code&#39; parameter as &#39;0xFFFFFFFFFFFFFFFF&#39;. The follow-on &#39;ngtcp2_conn_write_connection_close()&#39; serialises that value as a QUIC variable-length integer; because &#39;2^64-1&#39; exceeds the 62-bit varint ceiling, &#39;ngtcp2_put_uvarintlen()&#39; fails &#39;assert(n &lt; 4611686018427387904ULL)&#39; and the whole resolver process aborts. A remote, unauthenticated DoQ client can trigger this deterministically with a single QUIC connection by advertising &#39;initial_max_stream_data_bidi_local = 1&#39; in its transport parameters and sending one DoQ query without ever reading the stream.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-55991 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2492 <p>Ein Angreifer kann mehrere Schwachstellen in Unbound ausnutzen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Daten zu manipulieren, und um Sicherheitsvorkehrungen zu umgehen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Unbound ausnutzen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Daten zu manipulieren, und um Sicherheitsvorkehrungen zu umgehen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2492