<?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>Tue, 20 Oct 2026 10:53:48 +0000</lastBuildDate>
    <item>
      <title>cnvd-2018-26699</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2018-26699</link>
      <description>cnvd-2018-26699</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2018-26699</guid>
    </item>
    <item>
      <title>EUVD-2026-67150</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-67150</link>
      <description>EUVD-2026-67150</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-67150</guid>
    </item>
    <item>
      <title>fkie_cve-2018-14663</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2018-14663</link>
      <description>&lt;p&gt;An issue has been found in PowerDNS DNSDist before 1.3.3 allowing a remote attacker to craft a DNS query with trailing data such that the addition of a record by dnsdist, for example an OPT record when adding EDNS Client Subnet, might result in the trailing data being smuggled to the backend as a valid record while not seen by dnsdist. This is an issue when dnsdist is deployed as a DNS Firewall and used to filter some records that should not be received by the backend. This issue occurs only when either the &amp;#39;useClientSubnet&amp;#39; or the experimental &amp;#39;addXPF&amp;#39; parameters are used when declaring a new backend.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An issue has been found in PowerDNS DNSDist before 1.3.3 allowing a remote attacker to craft a DNS query with trailing data such that the addition of a record by dnsdist, for example an OPT record when adding EDNS Client Subnet, might result in the trailing data being smuggled to the backend as a valid record while not seen by dnsdist. This is an issue when dnsdist is deployed as a DNS Firewall and used to filter some records that should not be received by the backend. This issue occurs only when either the &amp;#39;useClientSubnet&amp;#39; or the experimental &amp;#39;addXPF&amp;#39; parameters are used when declaring a new backend.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2018-14663</guid>
    </item>
    <item>
      <title>GHSA-r2j7-9v32-854m</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-r2j7-9v32-854m</link>
      <description>&lt;p&gt;An issue has been found in PowerDNS DNSDist before 1.3.3 allowing a remote attacker to craft a DNS query with trailing data such that the addition of a record by dnsdist, for example an OPT record when adding EDNS Client Subnet, might result in the trailing data being smuggled to the backend as a valid record while not seen by dnsdist. This is an issue when dnsdist is deployed as a DNS Firewall and used to filter some records that should not be received by the backend. This issue occurs only when either the &amp;#39;useClientSubnet&amp;#39; or the experimental &amp;#39;addXPF&amp;#39; parameters are used when declaring a new backend.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An issue has been found in PowerDNS DNSDist before 1.3.3 allowing a remote attacker to craft a DNS query with trailing data such that the addition of a record by dnsdist, for example an OPT record when adding EDNS Client Subnet, might result in the trailing data being smuggled to the backend as a valid record while not seen by dnsdist. This is an issue when dnsdist is deployed as a DNS Firewall and used to filter some records that should not be received by the backend. This issue occurs only when either the &amp;#39;useClientSubnet&amp;#39; or the experimental &amp;#39;addXPF&amp;#39; parameters are used when declaring a new backend.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-r2j7-9v32-854m</guid>
    </item>
    <item>
      <title>gsd-2018-14663</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2018-14663</link>
      <description>gsd-2018-14663</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2018-14663</guid>
    </item>
    <item>
      <title>SUSE-SU-2023:2777-1 — Security update for dnsdist</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2023:2777-1</link>
      <description>&lt;p&gt;Security update for dnsdist&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for dnsdist&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2023:2777-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2018-14663</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2018-14663</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: dnsdist, Ubuntu:Pro:18.04:LTS: dnsdist&lt;/p&gt;
&lt;p&gt;An issue has been found in PowerDNS DNSDist before 1.3.3 allowing a remote attacker to craft a DNS query with trailing data such that the addition of a record by dnsdist, for example an OPT record when adding EDNS Client Subnet, might result in the trailing data being smuggled to the backend as a valid record while not seen by dnsdist. This is an issue when dnsdist is deployed as a DNS Firewall and used to filter some records that should not be received by the backend. This issue occurs only when either the &amp;#39;useClientSubnet&amp;#39; or the experimental &amp;#39;addXPF&amp;#39; parameters are used when declaring a new backend.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: dnsdist, Ubuntu:Pro:18.04:LTS: dnsdist&lt;/p&gt;
&lt;p&gt;An issue has been found in PowerDNS DNSDist before 1.3.3 allowing a remote attacker to craft a DNS query with trailing data such that the addition of a record by dnsdist, for example an OPT record when adding EDNS Client Subnet, might result in the trailing data being smuggled to the backend as a valid record while not seen by dnsdist. This is an issue when dnsdist is deployed as a DNS Firewall and used to filter some records that should not be received by the backend. This issue occurs only when either the &amp;#39;useClientSubnet&amp;#39; or the experimental &amp;#39;addXPF&amp;#39; parameters are used when declaring a new backend.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2018-14663</guid>
    </item>
  </channel>
</rss>
