<?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://127.0.0.1:10001</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>Thu, 19 Nov 2026 19:38:05 +0000</lastBuildDate>
    <item>
      <title>RUSTSEC-2026-0550 — Unsigned NSEC or NSEC3 record used in a nonexistence proof (hickory-proto)</title>
      <link>https://127.0.0.1:10001/vuln/rustsec-2026-0550</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 kept an NSEC or NSEC3 record for a nonexistence proof if any authority record with the same owner name had validated, not only if that record itself had. Someone who can answer or modify DNS responses could pair a correctly signed record with a forged NSEC or NSEC3 record of the same owner name and get a forged denial accepted as secure.&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 kept an NSEC or NSEC3 record for a nonexistence proof if any authority record with the same owner name had validated, not only if that record itself had. Someone who can answer or modify DNS responses could pair a correctly signed record with a forged NSEC or NSEC3 record of the same owner name and get a forged denial accepted as secure.&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://127.0.0.1:10001/vuln/rustsec-2026-0550</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-123590</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-123590</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 accept NSEC and NSEC3 records for DNSSEC nonexistence proofs when any other record with the same owner name passes signature validation. Attackers able to supply DNS responses can mix validly signed records with bogus same-name NSEC or NSEC3 records of different types in the authority section to forge 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 accept NSEC and NSEC3 records for DNSSEC nonexistence proofs when any other record with the same owner name passes signature validation. Attackers able to supply DNS responses can mix validly signed records with bogus same-name NSEC or NSEC3 records of different types in the authority section to forge nonexistence proofs.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-123590</guid>
    </item>
  </channel>
</rss>
