https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 19:45:23 +0000 https://vulnerability.circl.lu/vuln/fkie_cve-2026-44621 <p>With NLnet Labs Unbound up to and including version 1.25.1, applications using libunbound and configured with &#39;unwanted-reply-threshold&#39;, could eventually be abruptly terminated if the threshold is reached and libunbound needs to call &#39;libworker_alloc_cleanup&#39; since the function is absent from the function call allow list. When an application using libunbound sets &#39;unwanted-reply-threshold&#39; 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 &#39;libworker_alloc_cleanup&#39; 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 &#39;worker_alloc_cleanup&#39; is registed in the allow list and proceeds to perform the documented cache flush.</p> <p>With NLnet Labs Unbound up to and including version 1.25.1, applications using libunbound and configured with &#39;unwanted-reply-threshold&#39;, could eventually be abruptly terminated if the threshold is reached and libunbound needs to call &#39;libworker_alloc_cleanup&#39; since the function is absent from the function call allow list. When an application using libunbound sets &#39;unwanted-reply-threshold&#39; 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 &#39;libworker_alloc_cleanup&#39; 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 &#39;worker_alloc_cleanup&#39; is registed in the allow list and proceeds to perform the documented cache flush.</p> https://vulnerability.circl.lu/vuln/fkie_cve-2026-44621 https://vulnerability.circl.lu/vuln/ghsa-3m86-wjgw-cgqc <p>With NLnet Labs Unbound up to and including version 1.25.1, applications using libunbound and configured with &#39;unwanted-reply-threshold&#39;, could eventually be abruptly terminated if the threshold is reached and libunbound needs to call &#39;libworker_alloc_cleanup&#39; since the function is absent from the function call allow list. When an application using libunbound sets &#39;unwanted-reply-threshold&#39; 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 &#39;libworker_alloc_cleanup&#39; 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 &#39;worker_alloc_cleanup&#39; is registed in the allow list and proceeds to perform the documented cache flush.</p> <p>With NLnet Labs Unbound up to and including version 1.25.1, applications using libunbound and configured with &#39;unwanted-reply-threshold&#39;, could eventually be abruptly terminated if the threshold is reached and libunbound needs to call &#39;libworker_alloc_cleanup&#39; since the function is absent from the function call allow list. When an application using libunbound sets &#39;unwanted-reply-threshold&#39; 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 &#39;libworker_alloc_cleanup&#39; 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 &#39;worker_alloc_cleanup&#39; is registed in the allow list and proceeds to perform the documented cache flush.</p> https://vulnerability.circl.lu/vuln/ghsa-3m86-wjgw-cgqc https://vulnerability.circl.lu/vuln/msrc_cve-2026-44621 msrc_CVE-2026-44621 https://vulnerability.circl.lu/vuln/msrc_cve-2026-44621 https://vulnerability.circl.lu/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://vulnerability.circl.lu/vuln/oesa-2026-3333 https://vulnerability.circl.lu/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://vulnerability.circl.lu/vuln/opensuse-su-2026:11380-1 https://vulnerability.circl.lu/vuln/suse-su-2026:23050-1 <p>Security update for unbound</p> <p>Security update for unbound</p> https://vulnerability.circl.lu/vuln/suse-su-2026:23050-1 https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-44621 <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>With NLnet Labs Unbound up to and including version 1.25.1, applications using libunbound and configured with &#39;unwanted-reply-threshold&#39;, could eventually be abruptly terminated if the threshold is reached and libunbound needs to call &#39;libworker_alloc_cleanup&#39; since the function is absent from the function call allow list. When an application using libunbound sets &#39;unwanted-reply-threshold&#39; 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 &#39;libworker_alloc_cleanup&#39; 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 &#39;worker_alloc_cleanup&#39; is registed in the allow list and proceeds to perform the documented cache flush.</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>With NLnet Labs Unbound up to and including version 1.25.1, applications using libunbound and configured with &#39;unwanted-reply-threshold&#39;, could eventually be abruptly terminated if the threshold is reached and libunbound needs to call &#39;libworker_alloc_cleanup&#39; since the function is absent from the function call allow list. When an application using libunbound sets &#39;unwanted-reply-threshold&#39; 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 &#39;libworker_alloc_cleanup&#39; 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 &#39;worker_alloc_cleanup&#39; is registed in the allow list and proceeds to perform the documented cache flush.</p> https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-44621