<?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://vulnerability.circl.lu</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>Mon, 28 Sep 2026 14:19:22 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-89134</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-89134</link>
      <description>&lt;p&gt;A certificate with no dNSName SAN but another SAN type present (e.g. registeredID or iPAddress) bypassed the Subject CN dNSName name-constraint check. The CN-as-DNS fallback was gated on cert-&amp;gt;subjectCN != NULL &amp;amp;&amp;amp; cert-&amp;gt;altNames == NULL &amp;amp;&amp;amp; !cert-&amp;gt;isCA instead of &amp;#34;no dNSName SAN&amp;#34;, so an out-of-scope CN was accepted. This incomplete fix from CVE-2026-6731, leading to the name-constraint check issue, was introduced in wolfSSL version 5.9.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A certificate with no dNSName SAN but another SAN type present (e.g. registeredID or iPAddress) bypassed the Subject CN dNSName name-constraint check. The CN-as-DNS fallback was gated on cert-&amp;gt;subjectCN != NULL &amp;amp;&amp;amp; cert-&amp;gt;altNames == NULL &amp;amp;&amp;amp; !cert-&amp;gt;isCA instead of &amp;#34;no dNSName SAN&amp;#34;, so an out-of-scope CN was accepted. This incomplete fix from CVE-2026-6731, leading to the name-constraint check issue, was introduced in wolfSSL version 5.9.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-89134</guid>
    </item>
    <item>
      <title>GHSA-p2xv-vrwq-543q</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-p2xv-vrwq-543q</link>
      <description>&lt;p&gt;A certificate with no dNSName SAN but another SAN type present (e.g. registeredID or iPAddress) bypassed the Subject CN dNSName name-constraint check. The CN-as-DNS fallback was gated on cert-&amp;gt;subjectCN != NULL &amp;amp;&amp;amp; cert-&amp;gt;altNames == NULL &amp;amp;&amp;amp; !cert-&amp;gt;isCA instead of &amp;#34;no dNSName SAN&amp;#34;, so an out-of-scope CN was accepted. This incomplete fix from CVE-2026-6731, leading to the name-constraint check issue, was introduced in wolfSSL version 5.9.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A certificate with no dNSName SAN but another SAN type present (e.g. registeredID or iPAddress) bypassed the Subject CN dNSName name-constraint check. The CN-as-DNS fallback was gated on cert-&amp;gt;subjectCN != NULL &amp;amp;&amp;amp; cert-&amp;gt;altNames == NULL &amp;amp;&amp;amp; !cert-&amp;gt;isCA instead of &amp;#34;no dNSName SAN&amp;#34;, so an out-of-scope CN was accepted. This incomplete fix from CVE-2026-6731, leading to the name-constraint check issue, was introduced in wolfSSL version 5.9.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-p2xv-vrwq-543q</guid>
    </item>
  </channel>
</rss>
