<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-02T10:04:26.038234+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-339892</id>
    <title>EUVD-2026-339892</title>
    <updated>2026-10-02T10:04:26.118377+00:00</updated>
    <content>EUVD-2026-339892</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-339892"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-52684</id>
    <title>fkie_cve-2026-52684</title>
    <updated>2026-10-02T10:04:26.118419+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>If the auth responds very slowly and the records expire in between, the capping of TTLs is not enforced for lack of data. This does not happen on regular resolve as then then the 
child records are used immediately if not expired and thus valid, or the
 records are expired, and in that case not used.  So this case 
can only happen if almost expired records are used to refresh the 
authoritative NS records.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-52684"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-j58f-rgm2-v2p8</id>
    <title>GHSA-j58f-rgm2-v2p8</title>
    <updated>2026-10-02T10:04:26.118456+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>If the auth responds very slowly and the records expire in between, the capping of TTLs is not enforced for lack of data. This does not happen on regular resolve as then then the 
child records are used immediately if not expired and thus valid, or the
 records are expired, and in that case not used.  So this case 
can only happen if almost expired records are used to refresh the 
authoritative NS records.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-j58f-rgm2-v2p8"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-52684</id>
    <title>UBUNTU-CVE-2026-52684</title>
    <updated>2026-10-02T10:04:26.118475+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: pdns-recursor, Ubuntu:Pro:18.04:LTS: pdns-recursor, Ubuntu:Pro:20.04:LTS: pdns-recursor, Ubuntu:Pro:22.04:LTS: pdns-recursor, Ubuntu:24.04:LTS: pdns-recursor, Ubuntu:26.04:LTS: pdns-recursor</p>
<p>If the auth responds very slowly and the records expire in between, the capping of TTLs is not enforced for lack of data. This does not happen on regular resolve as then then the child records are used immediately if not expired and thus valid, or the  records are expired, and in that case not used.  So this case can only happen if almost expired records are used to refresh the authoritative NS records.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-52684"/>
  </entry>
</feed>
