CVE-2026-42769
Last modified
CVE-2026-42769 is a medium-severity vulnerability rated 5.3/10 on the CVSS scale. 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.. EPSS estimates a 0.26% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Openssl | Openssl | >= 3.4.0, < 3.4.6 |
| Openssl | Openssl | >= 3.5.0, < 3.5.7 |
| Openssl | Openssl | >= 3.6.0, < 3.6.3 |
| Openssl | Openssl | 4.0.0 |
References
- https://openssl-library.org/news/secadv/20260609.txtVendor Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-42769?
How severe is CVE-2026-42769?
How do I fix CVE-2026-42769?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-42763Missing Authorization vulnerability in SePay team SePay Gate…6.5
- CVE-2026-42764Issue summary: Receiving a QUIC initial packet with an inval…7.5
- CVE-2026-42765Issue summary: When a partial-chain certificate verification…7.5
- CVE-2026-42766Issue summary: A specially crafted password-encrypted CMS me…5.9
- CVE-2026-42767Issue summary: An attacker-controlled CMP (Certificate Manag…5.9
- CVE-2026-42768Issue summary: The CMS_decrypt and PKCS7_decrypt functions a…3.7
- CVE-2026-4277An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.…9.8
- CVE-2026-42770Issue summary: When EVP_PKEY_derive_set_peer() is called wit…3.7
- CVE-2026-42771Issue summary: When the X509_VERIFY_PARAM_set1_email is call…6.2
- CVE-2026-42773Improper Neutralization of Special Elements used in an SQL C…9.3
- CVE-2026-42774Improper Neutralization of Special Elements used in an SQL C…9.3
- CVE-2026-42775Unauthenticated Cross Site Scripting (XSS) in AutomatorWP <=…7.1
Are you affected by CVE-2026-42769?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
