<?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-18T05:43:10.997640+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-401955</id>
    <title>EUVD-2026-401955</title>
    <updated>2026-11-18T05:43:11.000694+00:00</updated>
    <content>EUVD-2026-401955</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-401955"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-123582</id>
    <title>fkie_cve-2026-123582</title>
    <updated>2026-11-18T05:43:11.000725+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>The validating recursive resolver and validating forwarder in Hickory DNS (hickory-server) 0.25.0 before 0.26.2 do not check whether the SOA record passed DNSSEC validation when assembling NXDOMAIN or NODATA responses. An attacker able to supply forged DNS responses can have a forged SOA record returned to clients with the AD bit set, misleading clients that rely on the server's DNSSEC validation.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-123582"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-p5hq-5ppr-f8g2</id>
    <title>GHSA-p5hq-5ppr-f8g2</title>
    <updated>2026-11-18T05:43:11.000758+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>The validating recursive resolver and validating forwarder in Hickory DNS (hickory-server) 0.25.0 before 0.26.2 do not check whether the SOA record passed DNSSEC validation when assembling NXDOMAIN or NODATA responses. An attacker able to supply forged DNS responses can have a forged SOA record returned to clients with the AD bit set, misleading clients that rely on the server's DNSSEC validation.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-p5hq-5ppr-f8g2"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2026-123582</id>
    <title>msrc_CVE-2026-123582 — Hickory DNS 0.25.0 before 0.26.2 DNSSEC Validation Bypass via SOA Record</title>
    <updated>2026-11-18T05:43:11.000777+00:00</updated>
    <content>msrc_CVE-2026-123582</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2026-123582"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-123582</id>
    <title>UBUNTU-CVE-2026-123582</title>
    <updated>2026-11-18T05:43:11.000794+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:26.10: rust-hickory-server, Ubuntu:26.04:LTS: rust-hickory-server</p>
<p>The validating recursive resolver and validating forwarder in Hickory DNS (hickory-server) 0.25.0 before 0.26.2 do not check whether the SOA record passed DNSSEC validation when assembling NXDOMAIN or NODATA responses. An attacker able to supply forged DNS responses can have a forged SOA record returned to clients with the AD bit set, misleading clients that rely on the server's DNSSEC validation.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-123582"/>
  </entry>
</feed>
