CVE-2026-42769
5.3 MEDIUMIssue Summary: An error in the callback used to verify the certificate provided in a Root CA key update Certificate Management Protocol (...
Published: 2026-06-09 · Last updated: 2026-06-09
Severity and scoring
- CVSS
- 5.3 MEDIUM
- Vector
- CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
- CWE
- CWE-295
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.
Source: NVD
References
- [NVD]https://nvd.nist.gov/vuln/detail/CVE-2026-42769
- [Other]https://github.com/openssl/security/commit/54d0989997e5fc26057009a9782c3441ce3842fb
- [Other]https://github.com/openssl/security/commit/777b363b16fcf2153bb3ded39dc3838713667c44
- [Other]https://github.com/openssl/security/commit/d35cd473a271bf3ce7bf3d32af53217fb83ae92c
- [Other]https://github.com/openssl/security/commit/d531f21c0fe99067a66fc0ff1161ef127f9cd70b
- [Other]https://openssl-library.org/news/secadv/20260609.txt
Related CVEs
Same CWE
- CVE-2026-41714 — Applications that configure their broker connection via RabbitConnectionFactoryBean.setUri("amqps://...") without also calling setUseSSL(... (4.0 MEDIUM)
- CVE-2026-50752 — A weakness in the certificate validation logic of the deprecated IKEv1 key exchange may allow an unauthenticated attacker positioned as a... (7.4 HIGH)
- CVE-2026-45745 — Termix is a web-based server management platform with SSH terminal, tunneling, and file editing capabilities (8.0 HIGH)
- CVE-2026-41859 — A network man-in-the-middle between nats-sync and the BOSH director can steal the director credentials (Basic auth header or UAA client s... (7.8 HIGH)
- CVE-2026-49267 — Apache Airflow's EmailOperator and the underlying `airflow.utils.email` helpers established SMTP STARTTLS connections without verifying t... (5.9 MEDIUM)