<?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>Wed, 07 Oct 2026 01:00:39 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-50243 — 'response-ip'/'rpz' can rewrite BOGUS answers instead of returning SERVFAIL</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-50243</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; NLnet Labs Unbound&lt;/p&gt;
&lt;p&gt;In NLnet Labs Unbound 1.6.2 up to and including 1.25.1, when Unbound is configured with the &amp;#39;respip&amp;#39; module in front of the validator together with a &amp;#39;response-ip&amp;#39; redirect rule or an RPZ file with an RPZ-IP trigger, the rewriting handler does not check the security status of the upstream answer and can instead rewrite a BOGUS A/AAAA answer to point to an operator&amp;#39;s configured IP. If the validator finds an expired or otherwise invalid RRSIG on an answer whose A record falls within a &amp;#39;response-ip&amp;#39;/RPZ configuration, the answer is still rewritten and given a hard coded security level of INSECURE. This results in the client receiving an INSECURE NOERROR reply rewritten by the operator&amp;#39;s configured IP. A malicious actor can exploit the possible poisonous effect by spoofing a BOGUS A/AAAA answer that falls inside the operator&amp;#39;s configured subnet rewrites. Such DNSSEC protected answers are then insecurely redirected to the operator&amp;#39;s configured target.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; NLnet Labs Unbound&lt;/p&gt;
&lt;p&gt;In NLnet Labs Unbound 1.6.2 up to and including 1.25.1, when Unbound is configured with the &amp;#39;respip&amp;#39; module in front of the validator together with a &amp;#39;response-ip&amp;#39; redirect rule or an RPZ file with an RPZ-IP trigger, the rewriting handler does not check the security status of the upstream answer and can instead rewrite a BOGUS A/AAAA answer to point to an operator&amp;#39;s configured IP. If the validator finds an expired or otherwise invalid RRSIG on an answer whose A record falls within a &amp;#39;response-ip&amp;#39;/RPZ configuration, the answer is still rewritten and given a hard coded security level of INSECURE. This results in the client receiving an INSECURE NOERROR reply rewritten by the operator&amp;#39;s configured IP. A malicious actor can exploit the possible poisonous effect by spoofing a BOGUS A/AAAA answer that falls inside the operator&amp;#39;s configured subnet rewrites. Such DNSSEC protected answers are then insecurely redirected to the operator&amp;#39;s configured target.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-50243</guid>
    </item>
  </channel>
</rss>
