<?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>Fri, 20 Nov 2026 21:52:55 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-84786 — Possible NULL Dereference in Non-SMTP DANE Clients</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-84786</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; OpenSSL&lt;/p&gt;
&lt;p&gt;Issue summary: A DANE-enabled TLS client may crash by dereferencing a NULL
pointer when processing an unusual combination of certificate and TLSA
records.&lt;/p&gt;
&lt;p&gt;Impact summary: The impact is limited to a client crash (potential Denial
of Service).&lt;/p&gt;
&lt;p&gt;CWE: CWE-476: NULL Pointer Dereference&lt;/p&gt;
&lt;p&gt;Description: A DANE-enabled TLS client that supports TLSA records with at
least one of the PKIX-TA(0) or PKIX-EE(1) usages alongside the DANE-TA(2)
usage may crash by dereferencing a NULL pointer if the server claims a trusted
CA&amp;#39;s certificate to be its end-entity certificate and has an unusual mix of
associated TLSA records.&lt;/p&gt;
&lt;p&gt;DANE SMTP clients should not be affected since only the
DANE-TA(2) and DANE-EE(3) TLSA record usages are specified applicable
in SMTP.  For example, the Postfix MTA is not affected, while the Exim
MTA does not at present use OpenSSL&amp;#39;s DANE implementation.&lt;/p&gt;
&lt;p&gt;Use of DANE in validation of RFC7250 raw public keys (RPKs) is also
unaffected, as these only use DANE-EE(3) TLSA records.&lt;/p&gt;
&lt;p&gt;Only applications that support combining the DANE PKI with a traditional PKI
are potentially affected.  A DANE-enabled browser or similar, that uses
OpenSSL&amp;#39;s DANE API could be affected.&lt;/p&gt;
&lt;p&gt;FIPS impact: no
The DANE API is outside the FIPS module boundary.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; OpenSSL&lt;/p&gt;
&lt;p&gt;Issue summary: A DANE-enabled TLS client may crash by dereferencing a NULL
pointer when processing an unusual combination of certificate and TLSA
records.&lt;/p&gt;
&lt;p&gt;Impact summary: The impact is limited to a client crash (potential Denial
of Service).&lt;/p&gt;
&lt;p&gt;CWE: CWE-476: NULL Pointer Dereference&lt;/p&gt;
&lt;p&gt;Description: A DANE-enabled TLS client that supports TLSA records with at
least one of the PKIX-TA(0) or PKIX-EE(1) usages alongside the DANE-TA(2)
usage may crash by dereferencing a NULL pointer if the server claims a trusted
CA&amp;#39;s certificate to be its end-entity certificate and has an unusual mix of
associated TLSA records.&lt;/p&gt;
&lt;p&gt;DANE SMTP clients should not be affected since only the
DANE-TA(2) and DANE-EE(3) TLSA record usages are specified applicable
in SMTP.  For example, the Postfix MTA is not affected, while the Exim
MTA does not at present use OpenSSL&amp;#39;s DANE implementation.&lt;/p&gt;
&lt;p&gt;Use of DANE in validation of RFC7250 raw public keys (RPKs) is also
unaffected, as these only use DANE-EE(3) TLSA records.&lt;/p&gt;
&lt;p&gt;Only applications that support combining the DANE PKI with a traditional PKI
are potentially affected.  A DANE-enabled browser or similar, that uses
OpenSSL&amp;#39;s DANE API could be affected.&lt;/p&gt;
&lt;p&gt;FIPS impact: no
The DANE API is outside the FIPS module boundary.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-84786</guid>
    </item>
  </channel>
</rss>
