<?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>Tue, 29 Sep 2026 07:27:29 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-42769 — Trust-Anchor Substitution via cert/issuer Typo in CMP rootCaKeyUpdate</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-42769</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; OpenSSL&lt;/p&gt;
&lt;p&gt;Issue Summary: An error in the callback used to verify the certificate
provided in a Root CA key update Certificate Management Protocol (CMP)
message response rendered the certificate validation ineffectual, which
could lead to escalation of credentials from the Registration Authority (RA)
level to the root Certification Authority (root CA) level.&lt;/p&gt;
&lt;p&gt;Impact Summary: The Registration Autority could replace the root CA
certificate for the CMP clients with an arbitrary root CA certificate.&lt;/p&gt;
&lt;p&gt;One of the parts of the Certificate Management Protocol (CMP), specified in
RFC 9810, is Root Certification Authority (root CA) key Rollover,
which is sent by the server in a message with type &amp;#39;id-it-rootCaKeyUpdate&amp;#39;.
As part of these messages, &amp;#39;newWithOld&amp;#39; certificate, the new root CA
certificate signed with the old root CA key, is provided, and verifying its
signature is crucial for transferring the trust from the old CA key to the
new one.&lt;/p&gt;
&lt;p&gt;The &amp;#39;id-it-rootCaKeyUpdate&amp;#39; messages are expected to be processed with
OSSL_CMP_get1_rootCaKeyUpdate(), that is expected to verify the &amp;#39;newWithOld&amp;#39;
certificate.  A typo in the certificate chain building code led to adding
an incorrect certificate (&amp;#39;newWithOld&amp;#39; instead of &amp;#39;oldRoot&amp;#39;) to the
certificate chain, rendering the certificate verification process ineffectual
(only the issuer name and the algorithm OIDs were verified by other parts
of the verification code).&lt;/p&gt;
&lt;p&gt;An attacker who already has credentials that satisfy the CMP message
protection checks can…&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: An error in the callback used to verify the certificate
provided in a Root CA key update Certificate Management Protocol (CMP)
message response rendered the certificate validation ineffectual, which
could lead to escalation of credentials from the Registration Authority (RA)
level to the root Certification Authority (root CA) level.&lt;/p&gt;
&lt;p&gt;Impact Summary: The Registration Autority could replace the root CA
certificate for the CMP clients with an arbitrary root CA certificate.&lt;/p&gt;
&lt;p&gt;One of the parts of the Certificate Management Protocol (CMP), specified in
RFC 9810, is Root Certification Authority (root CA) key Rollover,
which is sent by the server in a message with type &amp;#39;id-it-rootCaKeyUpdate&amp;#39;.
As part of these messages, &amp;#39;newWithOld&amp;#39; certificate, the new root CA
certificate signed with the old root CA key, is provided, and verifying its
signature is crucial for transferring the trust from the old CA key to the
new one.&lt;/p&gt;
&lt;p&gt;The &amp;#39;id-it-rootCaKeyUpdate&amp;#39; messages are expected to be processed with
OSSL_CMP_get1_rootCaKeyUpdate(), that is expected to verify the &amp;#39;newWithOld&amp;#39;
certificate.  A typo in the certificate chain building code led to adding
an incorrect certificate (&amp;#39;newWithOld&amp;#39; instead of &amp;#39;oldRoot&amp;#39;) to the
certificate chain, rendering the certificate verification process ineffectual
(only the issuer name and the algorithm OIDs were verified by other parts
of the verification code).&lt;/p&gt;
&lt;p&gt;An attacker who already has credentials that satisfy the CMP message
protection checks can…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-42769</guid>
    </item>
  </channel>
</rss>
