<?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>Thu, 01 Oct 2026 20:48:47 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-40622 — Another 'ghost domain names' attack variant</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-40622</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; NLnet Labs Unbound&lt;/p&gt;
&lt;p&gt;NLnet Labs Unbound 1.16.2 up to and including version 1.25.0 has a vulnerability of the &amp;#39;ghost domain names&amp;#39; family of attacks that could extend the ghost domain window by up to one cached TTL configured value. Similar to other &amp;#39;ghost domain names&amp;#39; attacks, an adversary needs to control a (ghost) zone and be able to query a vulnerable Unbound. A single client NS query can cause Unbound to overwrite the cached expired parent-side referral NS rrset with the child-side apex NS rrset and essentially extend the ghost domain window by up to one cached TTL configured value (&amp;#39;cache-max-ttl&amp;#39;). In configurations where &amp;#39;harden-referral-path: yes&amp;#39; is used (non-default configuration), no client NS query is required since Unbound implicitly performs that query. Unbound 1.25.1 contains a patch with a fix that does not allow extension of TTLs for (parent) NS records regardless of their trust.&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;NLnet Labs Unbound 1.16.2 up to and including version 1.25.0 has a vulnerability of the &amp;#39;ghost domain names&amp;#39; family of attacks that could extend the ghost domain window by up to one cached TTL configured value. Similar to other &amp;#39;ghost domain names&amp;#39; attacks, an adversary needs to control a (ghost) zone and be able to query a vulnerable Unbound. A single client NS query can cause Unbound to overwrite the cached expired parent-side referral NS rrset with the child-side apex NS rrset and essentially extend the ghost domain window by up to one cached TTL configured value (&amp;#39;cache-max-ttl&amp;#39;). In configurations where &amp;#39;harden-referral-path: yes&amp;#39; is used (non-default configuration), no client NS query is required since Unbound implicitly performs that query. Unbound 1.25.1 contains a patch with a fix that does not allow extension of TTLs for (parent) NS records regardless of their trust.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-40622</guid>
    </item>
  </channel>
</rss>
