<?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-11-17T14:49:41.183180+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/cve-2026-96888</id>
    <title>CVE-2026-96888 — Named may terminate unexpectedly when a redirect zone is used with strict QNAME minimization</title>
    <updated>2026-11-17T14:49:41.185095+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> ISC BIND 9</p>
<p>A BIND resolver that is configured with both a "redirect" zone and "qname-minimization strict" may abort with an assertion failure while processing the redirect.
This issue affects BIND 9 versions 9.16.0 through 9.18.50, 9.20.0 through 9.20.29, 9.21.0 through 9.21.26, 9.16.8-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.29-S1.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-96888"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/usn-8969-1</id>
    <title>USN-8969-1 — bind9 vulnerabilities</title>
    <updated>2026-11-17T14:49:41.185162+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:22.04:LTS: bind9, Ubuntu:24.04:LTS: bind9, Ubuntu:26.10: bind9, Ubuntu:26.04:LTS: bind9</p>
<p>It was discovered that Bind incorrectly handled certain DNS messages
with repeated singleton records such as SOA, CNAME, or DNAME records.
A remote attacker could possibly use this issue to cause Bind to use
excessive memory, leading to a denial of service. This issue only affected
Ubuntu 26.10. (CVE-2026-75029)</p>
<p>It was discovered that Bind incorrectly handled cached DNSSEC proofs.
A remote attacker could possibly use this issue to cause Bind to crash,
resulting in a denial of service. This issue only affected
Ubuntu 26.10. (CVE-2026-19662)</p>
<p>It was discovered that Bind incorrectly handled certain invalid DNSSEC
records. A remote attacker could possibly use this issue to cause Bind
to use excessive CPU resources, leading to a denial of service. This issue only affected
Ubuntu 26.10.
(CVE-2026-19668)</p>
<p>It was discovered that Bind incorrectly handled malformed answers on
resolvers configured to use DNS64. A remote attacker could possibly use
this issue to cause Bind to crash, resulting in a denial of service. This issue only affected
Ubuntu 26.10.
(CVE-2026-19666)</p>
<p>It was discovered that Bind incorrectly handled TKEY queries when no
global options block was present. A remote attacker could possibly use
this issue to cause Bind to crash, resulting in a denial of service.
This issue only affected
Ubuntu 26.10.
(CVE-2026-76163)</p>
<p>It was discovered that Bind incorrectly verified TSIG signatures during
zone transfers. A remote attacker could possibly use this issue to inject
unauthori…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/usn-8969-1"/>
  </entry>
</feed>
