<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 30 Sep 2026 10:44:56 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-44621 — Libunbound applications configured with 'unwanted-reply-threshold' could eventually be abruptly terminated</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-44621</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; NLnet Labs Unbound&lt;/p&gt;
&lt;p&gt;With NLnet Labs Unbound up to and including version 1.25.1, applications using libunbound and configured with &amp;#39;unwanted-reply-threshold&amp;#39;, could eventually be abruptly terminated if the threshold is reached and libunbound needs to call &amp;#39;libworker_alloc_cleanup&amp;#39; since the function is absent from the function call allow list. When an application using libunbound sets &amp;#39;unwanted-reply-threshold&amp;#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 &amp;#39;libworker_alloc_cleanup&amp;#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 &amp;#39;worker_alloc_cleanup&amp;#39; is registed in the allow list and proceeds to perform the documented cache flush.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; NLnet Labs Unbound&lt;/p&gt;
&lt;p&gt;With NLnet Labs Unbound up to and including version 1.25.1, applications using libunbound and configured with &amp;#39;unwanted-reply-threshold&amp;#39;, could eventually be abruptly terminated if the threshold is reached and libunbound needs to call &amp;#39;libworker_alloc_cleanup&amp;#39; since the function is absent from the function call allow list. When an application using libunbound sets &amp;#39;unwanted-reply-threshold&amp;#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 &amp;#39;libworker_alloc_cleanup&amp;#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 &amp;#39;worker_alloc_cleanup&amp;#39; is registed in the allow list and proceeds to perform the documented cache flush.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-44621</guid>
    </item>
  </channel>
</rss>
