<?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-16T21:06:45.188607+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-401954</id>
    <title>EUVD-2026-401954</title>
    <updated>2026-11-16T21:06:45.192898+00:00</updated>
    <content>EUVD-2026-401954</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-401954"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-123581</id>
    <title>fkie_cve-2026-123581</title>
    <updated>2026-11-16T21:06:45.192936+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Hickory DNS hickory-proto through 0.26.0-alpha.1 and hickory-net 0.26.0-beta.1 before 0.26.2 contain a DNSSEC validation flaw that accepts a response as a positive answer when any valid RRset appears in the answer section, without checking that the RRset is responsive to the query. Attackers can supply signed but unrelated RRsets so that responses lacking matching records are validated as positive answers instead of as no-data responses.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-123581"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-6w9h-68h2-v6xq</id>
    <title>GHSA-6w9h-68h2-v6xq</title>
    <updated>2026-11-16T21:06:45.192980+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Hickory DNS hickory-proto through 0.26.0-alpha.1 and hickory-net 0.26.0-beta.1 before 0.26.2 contain a DNSSEC validation flaw that accepts a response as a positive answer when any valid RRset appears in the answer section, without checking that the RRset is responsive to the query. Attackers can supply signed but unrelated RRsets so that responses lacking matching records are validated as positive answers instead of as no-data responses.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-6w9h-68h2-v6xq"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2026-123581</id>
    <title>msrc_CVE-2026-123581 — Hickory DNS through 0.26.0-alpha.1 DNSSEC Validation Bypass via Unrelated RRset</title>
    <updated>2026-11-16T21:06:45.193011+00:00</updated>
    <content>msrc_CVE-2026-123581</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2026-123581"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rustsec-2026-0512</id>
    <title>RUSTSEC-2026-0512 — DNSSEC validation accepted an unrelated signed RRset as the answer (hickory-proto)</title>
    <updated>2026-11-16T21:06:45.193036+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 treated a response with a non-empty answer section as a positive answer if its records validated, without checking that any of them matched the queried name and type. Someone who can answer or modify DNS responses could return a genuine signed RRset for another name or type and have it accepted as a validated answer.</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-0512"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-123581</id>
    <title>UBUNTU-CVE-2026-123581</title>
    <updated>2026-11-16T21:06:45.193085+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-proto through 0.26.0-alpha.1 and hickory-net 0.26.0-beta.1 before 0.26.2 contain a DNSSEC validation flaw that accepts a response as a positive answer when any valid RRset appears in the answer section, without checking that the RRset is responsive to the query. Attackers can supply signed but unrelated RRsets so that responses lacking matching records are validated as positive answers instead of as no-data responses.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-123581"/>
  </entry>
</feed>
