<?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-16T19:38:20.114123+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-401953</id>
    <title>EUVD-2026-401953</title>
    <updated>2026-11-16T19:38:20.118114+00:00</updated>
    <content>EUVD-2026-401953</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-401953"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-123580</id>
    <title>fkie_cve-2026-123580</title>
    <updated>2026-11-16T19:38:20.118147+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Hickory DNS hickory-net 0.26.0-beta.1 before 0.26.2 and hickory-proto through 0.26.0-alpha.1 perform insufficient checks on NSEC3 record names during DNSSEC verification, comparing only the hashed label without confirming the record belongs to the correct zone. Attackers can supply NSEC3 records from another zone with a matching hash label to forge DNSSEC nonexistence proofs.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-123580"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-wgx4-v7mx-crxr</id>
    <title>GHSA-wgx4-v7mx-crxr</title>
    <updated>2026-11-16T19:38:20.118178+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Hickory DNS hickory-net 0.26.0-beta.1 before 0.26.2 and hickory-proto through 0.26.0-alpha.1 perform insufficient checks on NSEC3 record names during DNSSEC verification, comparing only the hashed label without confirming the record belongs to the correct zone. Attackers can supply NSEC3 records from another zone with a matching hash label to forge DNSSEC nonexistence proofs.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-wgx4-v7mx-crxr"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2026-123580</id>
    <title>msrc_CVE-2026-123580 — Hickory-DNS 0.26.0-beta.1 before 0.26.2 DNSSEC Nonexistence Proof Forgery via NSEC3</title>
    <updated>2026-11-16T19:38:20.118195+00:00</updated>
    <content>msrc_CVE-2026-123580</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2026-123580"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rustsec-2026-0505</id>
    <title>RUSTSEC-2026-0505 — NSEC3 owner names not checked against the zone in DNSSEC validation (hickory-proto)</title>
    <updated>2026-11-16T19:38:20.118212+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: hickory-proto</p>
<p>Up to 0.26.0-alpha.1, hickory-proto's DNSSEC validation matched NSEC3 records to a name only by the hashed first label of the NSEC3 owner name, without checking that the rest of the owner name was the zone in question. A signed NSEC3 record from any zone the attacker controls could therefore be used, by someone who can answer or modify DNS responses, to prove that a name in another zone does not exist.</p>
<p>From 0.26.0-beta.1 the DNSSEC validation code lives in the hickory-net crate, where this was fixed in hickory-net 0.26.2. No hickory-proto release contains a fix. Users of DNSSEC validation in older hickory-proto releases (directly or through hickory-resolver or hickory-recursor) should move to the 0.26.2 or later releases, which validate through hickory-net.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rustsec-2026-0505"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-123580</id>
    <title>UBUNTU-CVE-2026-123580</title>
    <updated>2026-11-16T19:38:20.118238+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:24.04:LTS: rust-hickory-proto, Ubuntu:26.10: rust-hickory-net, Ubuntu:26.10: rust-hickory-proto, Ubuntu:26.04:LTS: rust-hickory-proto</p>
<p>Hickory DNS hickory-net 0.26.0-beta.1 before 0.26.2 and hickory-proto through 0.26.0-alpha.1 perform insufficient checks on NSEC3 record names during DNSSEC verification, comparing only the hashed label without confirming the record belongs to the correct zone. Attackers can supply NSEC3 records from another zone with a matching hash label to forge DNSSEC nonexistence proofs.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-123580"/>
  </entry>
</feed>
