<?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-09T08:52:01.500796+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-11331</id>
    <title>CVE-2026-11331 — Potential wildcard CNAME RPZ policy bypass</title>
    <updated>2026-10-09T08:52:01.523575+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> ISC BIND 9</p>
<p>An attacker who knows (or guesses) that a resolver uses RPZ with wildcard CNAME policies can craft query names long enough to trigger a NAMETOOLONG error condition during RPZ processing. This is not handled correctly and may lead to defeating the RPZ rule. It also may lead to an unexpected exit of the BIND 9 software.
This issue affects BIND 9 versions 9.16.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.16.8-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-11331"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/usn-8648-1</id>
    <title>USN-8648-1 — bind9 vulnerabilities</title>
    <updated>2026-10-09T08:52:01.523648+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.04:LTS: bind9</p>
<p>It was discovered that Bind incorrectly accepted NSEC3 records whose signer
name did not match the owning zone. A remote attacker could possibly use
this issue to perform NSEC3 impersonation attacks, bypassing DNSSEC
validation. (CVE-2026-10723)</p>
<p>It was discovered that Bind incorrectly handled Key Records using the
PRIVATEDNS algorithm. A remote attacker could possibly use this issue to
cause Bind to crash, resulting in a denial of service. (CVE-2026-10822)</p>
<p>It was discovered that Bind incorrectly handled wildcard CNAME expansion in
Response Policy Zones. A remote attacker could possibly use this issue to
bypass configured RPZ policies. (CVE-2026-11331)</p>
<p>It was discovered that Bind performed unnecessary validation of DNSSEC
signed records. A remote attacker could possibly use this issue to cause
Bind to use excessive resources, leading to a denial of service. This issue
only affected Ubuntu 26.04 LTS. (CVE-2026-11605)</p>
<p>It was discovered that Bind incorrectly tracked memory usage in the DNS
cache. A remote attacker could possibly use this issue to cause Bind to use
memory beyond configured limits, leading to a denial of service.
(CVE-2026-11622)</p>
<p>It was discovered that Bind incorrectly handled signed wildcard records
with label count discrepancies and RRSIG validation. A remote attacker
could possibly use this issue to perform cache poisoning attacks.
(CVE-2026-11721)</p>
<p>It was discovered that Bind incorrectly handled certain CNAME and DNAME
record orderings in the resolver. A…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/usn-8648-1"/>
  </entry>
</feed>
