https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 05:34:42 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-339892 EUVD-2026-339892 https://cve.radiocsirt.org/vuln/euvd-2026-339892 https://cve.radiocsirt.org/vuln/fkie_cve-2026-52684 <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> <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> https://cve.radiocsirt.org/vuln/fkie_cve-2026-52684 https://cve.radiocsirt.org/vuln/ghsa-j58f-rgm2-v2p8 <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> <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> https://cve.radiocsirt.org/vuln/ghsa-j58f-rgm2-v2p8 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-52684 <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> <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> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-52684