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.
Impact Summary: The Registration Autority could replace the root CA certificate for the CMP clients with an arbitrary root CA certificate.
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 'id-it-rootCaKeyUpdate'. As part of these messages, 'newWithOld' 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.
The 'id-it-rootCaKeyUpdate' messages are expected to be processed with OSSL_CMP_get1_rootCaKeyUpdate(), that is expected to verify the 'newWithOld' certificate. A typo in the certificate chain building code led to adding an incorrect certificate ('newWithOld' instead of 'oldRoot') 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).
An attacker who already has credentials that satisfy the CMP message protection checks can generate a new key pair and use a crafted self-signed certificate in its 'id-it-rootCaKeyUpdate' CMP messages which affected CMP clients would accept as a new trust anchor.
Significant preconditions for the attack (having valid RA-level credentials) are the reason the issue was assigned Low severity.
The FIPS modules are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.
CVSS Details
- CVSS 3.1 Base Score: 5.3
- CVSS 3.1 Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N)
Covered by Rapid7
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Alma_linux | — | Upgrade openssl-develUpgrade openssl-libsUpgrade opensslUpgrade openssl-perl | Jun 16, 2026 | Jun 11, 2026 |
| Alpine Linux | — | Upgrade openssl | Jun 18, 2026 | Jun 9, 2026 |
| Amazon_linux_2023 | — | Upgrade openssl-develUpgrade openssl-libsUpgrade openssl-fips-provider-latestUpgrade openssl-debuginfoUpgrade opensslUpgrade openssl-snapsafe-libsUpgrade openssl-snapsafe-libs-debuginfoUpgrade openssl-debugsourceUpgrade openssl-fips-provider-latest-debuginfoUpgrade openssl-perlUpgrade openssl-libs-debuginfo | Jun 23, 2026 | Jun 9, 2026 |
| Debian | — | Upgrade openssl | Jul 23, 2026 | Jul 23, 2026 |
| Freebsd | — | Upgrade opensslUpgrade openssl35Upgrade openssl36Upgrade openssl111Upgrade openssl34Upgrade openssl40Upgrade FreeBSD | Jun 15, 2026 | Jun 10, 2026 |
| Http Openssl | — | Upgrade to the latest version of OpenSSL | Jun 10, 2026 | Jun 9, 2026 |
| Oracle Missing Cpu Jul 2026 | — | Apply the July 2026 Critical Patch Update (CPU) for Oracle Database | Jul 22, 2026 | Jun 9, 2026 |
| Redhat_linux | — | Upgrade openssl-develUpgrade openssl-debugsourceUpgrade openssl-libsUpgrade openssl-debuginfoUpgrade openssl-libs-debuginfoUpgrade opensslUpgrade openssl-perlNo solution exists | Jun 17, 2026 | Jun 9, 2026 |
| Rocky_linux | — | Upgrade openssl-perlUpgrade opensslUpgrade openssl-debugsourceUpgrade openssl-debuginfoUpgrade openssl-libsUpgrade openssl-libs-debuginfoUpgrade openssl-devel | Jun 17, 2026 | Jun 13, 2026 |
| Ubuntu | — | Upgrade libssl3Upgrade opensslUpgrade libssl3t64 | Jun 16, 2026 | Jun 9, 2026 |
| Vmware Photon_os | — | Use 'tdnf update' to upgrade all packages to the latest version. | Jun 18, 2026 | Jun 9, 2026 |
Prioritise with Active Threat Intelligence
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub