https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 23:41:51 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-339347 EUVD-2026-339347 https://cve.radiocsirt.org/vuln/euvd-2026-339347 https://cve.radiocsirt.org/vuln/fkie_cve-2026-56416 <p>In NLnet Labs Unbound up to and including version 1.25.1, when the validator builds the canonical RDATA form for an RRSIG-covered PX/RP/MINFO/SOA RRset, it computes the address of the second embedded domain name as &#39;datstart + dname_valid(datstart, ...)&#39; and passes it straight to &#39;query_dname_tolower()&#39; without checking that a second name is actually present in the RDATA. The wire-format parser accepts multi-dname RRs whose RDATA ends after the first name, so an attacker who runs a DNSSEC-signed authoritative server can deliver a record with an absent second domain name (e.g. SOA record) and cause &#39;query_dname_tolower()&#39; to walk label-by-label through stale bytes in the per-worker &#39;env-&gt;scratch_buffer&#39;, past the end of that heap allocation if &#39;msg-buffer-size&#39; has been lowered from the default. This leads to heap buffer overflow and on a release build the outcome relies heavily on the contents of the buffer tail and the adjacent heap chunk.</p> <p>In NLnet Labs Unbound up to and including version 1.25.1, when the validator builds the canonical RDATA form for an RRSIG-covered PX/RP/MINFO/SOA RRset, it computes the address of the second embedded domain name as &#39;datstart + dname_valid(datstart, ...)&#39; and passes it straight to &#39;query_dname_tolower()&#39; without checking that a second name is actually present in the RDATA. The wire-format parser accepts multi-dname RRs whose RDATA ends after the first name, so an attacker who runs a DNSSEC-signed authoritative server can deliver a record with an absent second domain name (e.g. SOA record) and cause &#39;query_dname_tolower()&#39; to walk label-by-label through stale bytes in the per-worker &#39;env-&gt;scratch_buffer&#39;, past the end of that heap allocation if &#39;msg-buffer-size&#39; has been lowered from the default. This leads to heap buffer overflow and on a release build the outcome relies heavily on the contents of the buffer tail and the adjacent heap chunk.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-56416 https://cve.radiocsirt.org/vuln/ghsa-2845-97v4-7wm3 <p>In NLnet Labs Unbound up to and including version 1.25.1, when the validator builds the canonical RDATA form for an RRSIG-covered PX/RP/MINFO/SOA RRset, it computes the address of the second embedded domain name as &#39;datstart + dname_valid(datstart, ...)&#39; and passes it straight to &#39;query_dname_tolower()&#39; without checking that a second name is actually present in the RDATA. The wire-format parser accepts multi-dname RRs whose RDATA ends after the first name, so an attacker who runs a DNSSEC-signed authoritative server can deliver a record with an absent second domain name (e.g. SOA record) and cause &#39;query_dname_tolower()&#39; to walk label-by-label through stale bytes in the per-worker &#39;env-&gt;scratch_buffer&#39;, past the end of that heap allocation if &#39;msg-buffer-size&#39; has been lowered from the default. This leads to heap buffer overflow and on a release build the outcome relies heavily on the contents of the buffer tail and the adjacent heap chunk.</p> <p>In NLnet Labs Unbound up to and including version 1.25.1, when the validator builds the canonical RDATA form for an RRSIG-covered PX/RP/MINFO/SOA RRset, it computes the address of the second embedded domain name as &#39;datstart + dname_valid(datstart, ...)&#39; and passes it straight to &#39;query_dname_tolower()&#39; without checking that a second name is actually present in the RDATA. The wire-format parser accepts multi-dname RRs whose RDATA ends after the first name, so an attacker who runs a DNSSEC-signed authoritative server can deliver a record with an absent second domain name (e.g. SOA record) and cause &#39;query_dname_tolower()&#39; to walk label-by-label through stale bytes in the per-worker &#39;env-&gt;scratch_buffer&#39;, past the end of that heap allocation if &#39;msg-buffer-size&#39; has been lowered from the default. This leads to heap buffer overflow and on a release build the outcome relies heavily on the contents of the buffer tail and the adjacent heap chunk.</p> https://cve.radiocsirt.org/vuln/ghsa-2845-97v4-7wm3 https://cve.radiocsirt.org/vuln/msrc_cve-2026-56416 msrc_CVE-2026-56416 https://cve.radiocsirt.org/vuln/msrc_cve-2026-56416 https://cve.radiocsirt.org/vuln/oesa-2026-3333 <p><strong>Affected:</strong> openEuler:22.03-LTS-SP4: unbound</p> <p>Unbound is a validating, recursive, caching DNS resolver. It is designed to be fast and lean and incorporates modern features based on open standards. To help increase online privacy, Unbound supports DNS-over-TLS which allows clients to encrypt their communication. Unbound is available for most platforms such as FreeBSD, OpenBSD, NetBSD, MacOS, Linux and Microsoft Windows. Unbound is a totally free, open source software under the BSD license. It doesn&amp;amp;apos;t make custom builds or provide specific features to paying customers only. Security Fix(es):</p> <p>With NLnet Labs Unbound up to and including version 1.25.1, applications using libunbound and configured with &amp;apos;unwanted-reply-threshold&amp;apos;, could eventually be abruptly terminated if the threshold is reached and libunbound needs to call &amp;apos;libworker_alloc_cleanup&amp;apos; since the function is absent from the function call allow list. When an application using libunbound sets &amp;apos;unwanted-reply-threshold&amp;apos; to any non-zero value and the iterator queries an authoritative that replies with enough wrong-transaction-ID UDP datagrams to cross the threshold, the &amp;apos;libworker_alloc_cleanup&amp;apos; will eventually be called. Since the function is absent from the function call allow list, this leads to a fatal exit of libunbound and eventual termination of the embedding application.Unbound itself is not affected since its relevant function &amp;apos;worker_alloc_cleanup&amp;apos; is registed in the allow list and proceeds to…</p> <p><strong>Affected:</strong> openEuler:22.03-LTS-SP4: unbound</p> <p>Unbound is a validating, recursive, caching DNS resolver. It is designed to be fast and lean and incorporates modern features based on open standards. To help increase online privacy, Unbound supports DNS-over-TLS which allows clients to encrypt their communication. Unbound is available for most platforms such as FreeBSD, OpenBSD, NetBSD, MacOS, Linux and Microsoft Windows. Unbound is a totally free, open source software under the BSD license. It doesn&amp;amp;apos;t make custom builds or provide specific features to paying customers only. Security Fix(es):</p> <p>With NLnet Labs Unbound up to and including version 1.25.1, applications using libunbound and configured with &amp;apos;unwanted-reply-threshold&amp;apos;, could eventually be abruptly terminated if the threshold is reached and libunbound needs to call &amp;apos;libworker_alloc_cleanup&amp;apos; since the function is absent from the function call allow list. When an application using libunbound sets &amp;apos;unwanted-reply-threshold&amp;apos; to any non-zero value and the iterator queries an authoritative that replies with enough wrong-transaction-ID UDP datagrams to cross the threshold, the &amp;apos;libworker_alloc_cleanup&amp;apos; will eventually be called. Since the function is absent from the function call allow list, this leads to a fatal exit of libunbound and eventual termination of the embedding application.Unbound itself is not affected since its relevant function &amp;apos;worker_alloc_cleanup&amp;apos; is registed in the allow list and proceeds to…</p> https://cve.radiocsirt.org/vuln/oesa-2026-3333 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-56416 <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 up to and including version 1.25.1, when the validator builds the canonical RDATA form for an RRSIG-covered PX/RP/MINFO/SOA RRset, it computes the address of the second embedded domain name as &#39;datstart + dname_valid(datstart, ...)&#39; and passes it straight to &#39;query_dname_tolower()&#39; without checking that a second name is actually present in the RDATA. The wire-format parser accepts multi-dname RRs whose RDATA ends after the first name, so an attacker who runs a DNSSEC-signed authoritative server can deliver a record with an absent second domain name (e.g. SOA record) and cause &#39;query_dname_tolower()&#39; to walk label-by-label through stale bytes in the per-worker &#39;env-&gt;scratch_buffer&#39;, past the end of that heap allocation if &#39;msg-buffer-size&#39; has been lowered from the default. This leads to heap buffer overflow and on a release build the outcome relies heavily on the contents of the buffer tail and the adjacent heap chunk.</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 up to and including version 1.25.1, when the validator builds the canonical RDATA form for an RRSIG-covered PX/RP/MINFO/SOA RRset, it computes the address of the second embedded domain name as &#39;datstart + dname_valid(datstart, ...)&#39; and passes it straight to &#39;query_dname_tolower()&#39; without checking that a second name is actually present in the RDATA. The wire-format parser accepts multi-dname RRs whose RDATA ends after the first name, so an attacker who runs a DNSSEC-signed authoritative server can deliver a record with an absent second domain name (e.g. SOA record) and cause &#39;query_dname_tolower()&#39; to walk label-by-label through stale bytes in the per-worker &#39;env-&gt;scratch_buffer&#39;, past the end of that heap allocation if &#39;msg-buffer-size&#39; has been lowered from the default. This leads to heap buffer overflow and on a release build the outcome relies heavily on the contents of the buffer tail and the adjacent heap chunk.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-56416 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