<?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://cve.radiocsirt.org</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>Tue, 06 Oct 2026 16:18:03 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-55717 — 'serve-expired-client-timeout' and 'response-ip' CNAME redirect could lead to a crash</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-55717</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; NLnet Labs Unbound&lt;/p&gt;
&lt;p&gt;In NLnet Labs Unbound 1.10.0 up to and including 1.25.1, when &amp;#39;serve-expired: yes&amp;#39; is set together with a &amp;#39;response-ip: &amp;lt;net&amp;gt; redirect&amp;#39; /&amp;#39;response-ip-data: &amp;lt;net&amp;gt; CNAME &amp;lt;target&amp;gt;&amp;#39; rule (or the RPZ &amp;#39;rpz-cname-override&amp;#39; equivalent), a remote client who controls any delegated domain can crash the daemon. The serve-expired-client-timeout callback runs a two-pass loop to chase the respip-generated CNAME alias; on the second pass it resets &amp;#39;alias_rrset&amp;#39; but not &amp;#39;partial_rep&amp;#39;. Later, this inconsistency leads to a NULL pointer dereference and an eventual crash. A malicious actor can exploit the vulnerability by controlling any zone that replies with an A/AAAA record that falls inside the configured response-ip/rpz subnet. By delaying the answer when the previous record has expired, the vulnerable path of &amp;#39;serve-expired-client-timeout&amp;#39; is taken leading to denial of service via the server crash.&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;In NLnet Labs Unbound 1.10.0 up to and including 1.25.1, when &amp;#39;serve-expired: yes&amp;#39; is set together with a &amp;#39;response-ip: &amp;lt;net&amp;gt; redirect&amp;#39; /&amp;#39;response-ip-data: &amp;lt;net&amp;gt; CNAME &amp;lt;target&amp;gt;&amp;#39; rule (or the RPZ &amp;#39;rpz-cname-override&amp;#39; equivalent), a remote client who controls any delegated domain can crash the daemon. The serve-expired-client-timeout callback runs a two-pass loop to chase the respip-generated CNAME alias; on the second pass it resets &amp;#39;alias_rrset&amp;#39; but not &amp;#39;partial_rep&amp;#39;. Later, this inconsistency leads to a NULL pointer dereference and an eventual crash. A malicious actor can exploit the vulnerability by controlling any zone that replies with an A/AAAA record that falls inside the configured response-ip/rpz subnet. By delaying the answer when the previous record has expired, the vulnerable path of &amp;#39;serve-expired-client-timeout&amp;#39; is taken leading to denial of service via the server crash.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-55717</guid>
    </item>
  </channel>
</rss>
