CVE-2026-42769
CVE-2026-42769 is a medium-severity vulnerability in Openssl with a CVSS 3.x base score of 5.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-295.
Key facts
- Severity: Medium (CVSS 3.x base score 5.3)
- EPSS exploit prediction: 1% (47th percentile)
- Actively exploited: Not listed in CISA KEV
- EU (EUVD) id: EUVD-2026-35486
- Weakness: CWE-295
- Affected product: Openssl
- Published:
- Last modified:
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.
Frequently asked questions
- What is CVE-2026-42769?
- 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.
- How severe is CVE-2026-42769?
- CVE-2026-42769 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
- Is CVE-2026-42769 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (47th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2026-42769?
- CVE-2026-42769 primarily affects Openssl. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
- How do I fix CVE-2026-42769?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- Does CVE-2026-42769 have an EU (EUVD) identifier?
- Yes. CVE-2026-42769 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-35486.
- When was CVE-2026-42769 published?
- CVE-2026-42769 was published on 2026-06-09 and last updated on 2026-07-23.
References
- https://github.com/openssl/openssl/commit/54d0989997e5fc26057009a9782c3441ce3842fb
- https://github.com/openssl/openssl/commit/777b363b16fcf2153bb3ded39dc3838713667c44
- https://github.com/openssl/openssl/commit/d35cd473a271bf3ce7bf3d32af53217fb83ae92c
- https://github.com/openssl/openssl/commit/d531f21c0fe99067a66fc0ff1161ef127f9cd70b
- https://openssl-library.org/news/secadv/20260609.txt
Affected products (2)
- cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:*
- cpe:2.3:a:openssl:openssl:4.0.0:-:*:*:*:*:*:*
More vulnerabilities in Openssl
- CVE-2009-3245 — Critical (CVSS 10.0): OpenSSL before 0.9.8m does not check for a NULL return value from bn_wexpand function calls in (1) crypto/bn/bn_div.c,…
- CVE-2006-3738 — Critical (CVSS 10.0): Buffer overflow in the SSL_get_shared_ciphers function in OpenSSL 0.9.7 before 0.9.7l, 0.9.8 before 0.9.8d, and earlier…
- CVE-2026-63073 — Critical (CVSS 9.8): Issue summary: OpenSSL CMP response validation passed an unexpected response sender distinguished name directly as the…
- CVE-2026-31789 — Critical (CVSS 9.8): Issue summary: Converting an excessively large OCTET STRING value to a hexadecimal string leads to a heap buffer…
- CVE-2025-9230 — Critical (CVSS 9.8): Issue summary: An application trying to decrypt CMS messages encrypted using password based encryption can trigger an…
- CVE-2024-4741 — Critical (CVSS 9.8): Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause memory to be accessed that was previously…
Other CWE-295 (Improper Certificate Validation) vulnerabilities
- CVE-2026-75521 — Critical (CVSS 10.0): Miren Runtime provides the runtime component for the Miren application platform. Prior to 0.11.1, the QUIC/HTTP3 RPC…
- CVE-2026-112816 — Critical (CVSS 10.0): Improper certificate validation in the HTTPS listener in Canonical LXD 4.0.14, 5.0.10, 5.21.8, 6.9 before 4.0.15,…
- CVE-2026-111815 — Critical (CVSS 10.0): Apache Traffic Server can resume a TLS session across SNI virtual hosts without re-verifying a client certificate…
- CVE-2026-111814 — Critical (CVSS 10.0): Apache Traffic Server's default outbound session-sharing policy can reuse a pooled TLS session authenticated with one…
- CVE-2026-96207 — Critical (CVSS 10.0): Improper certificate validation in Microsoft Partner Center allows an unauthorized attacker to elevate privileges over…
- CVE-2026-58162 — Critical (CVSS 10.0): The Apache Traffic Server certifier plugin generates certificates based on attacker-controlled client SNI. This…
Browse all CWE-295 (Improper Certificate Validation) vulnerabilities →
Threat intelligence
Threat-intel indicators referencing this CVE:
- 137.184.52.40 (ipv4-addr)
- 169.58.222.110 (ipv4-addr)
- 217.216.41.224 (ipv4-addr)
- 37.120.144.165 (ipv4-addr)
- 167.160.88.250 (ipv4-addr)
- 132.248.246.162 (ipv4-addr)
- 195.191.219.70 (ipv4-addr)
- 46.235.42.53 (ipv4-addr)