<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 16 Nov 2026 19:38:07 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-401953</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-401953</link>
      <description>EUVD-2026-401953</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-401953</guid>
    </item>
    <item>
      <title>fkie_cve-2026-123580</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-123580</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-123580</guid>
    </item>
    <item>
      <title>GHSA-wgx4-v7mx-crxr</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-wgx4-v7mx-crxr</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-wgx4-v7mx-crxr</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-123580 — Hickory-DNS 0.26.0-beta.1 before 0.26.2 DNSSEC Nonexistence Proof Forgery via NSEC3</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-123580</link>
      <description>msrc_CVE-2026-123580</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-123580</guid>
    </item>
    <item>
      <title>RUSTSEC-2026-0505 — NSEC3 owner names not checked against the zone in DNSSEC validation (hickory-proto)</title>
      <link>https://cve.radiocsirt.org/vuln/rustsec-2026-0505</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: hickory-proto&lt;/p&gt;
&lt;p&gt;Up to 0.26.0-alpha.1, hickory-proto&amp;#39;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: hickory-proto&lt;/p&gt;
&lt;p&gt;Up to 0.26.0-alpha.1, hickory-proto&amp;#39;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rustsec-2026-0505</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-123580</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-123580</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-123580</guid>
    </item>
  </channel>
</rss>
