Threats Tagged 'cve-2026-42789'

Two security vulnerabilities were identified in the Erlang OTP public_key module used by Red Hat OpenStack Services on OpenShift 18.0. These include a certificate chain forgery vulnerability due to improper trust chain validation (CVE-2026-42789) and a certificate validation bypass that allows hostname spoofing (CVE-2026-42790). Red Hat has issued an important security update addressing these issues. The vulnerabilities relate to improper certificate validation which could undermine trust in secure communications. No CVSS score is provided, but the impact is rated as high by Red Hat. A security update is available and should be applied to affected systems. No known exploits in the wild have been reported at this time.

Improper Following of a Certificate's Chain of Trust vulnerability in Erlang OTP public_key (pubkey_cert module) allows a non-CA certificate to be accepted as an intermediate issuer, enabling certificate chain forgery. In lib/public_key/src/pubkey_cert.erl, pubkey_cert:validate_extensions/7 contains two flaws that together allow a certificate with basicConstraints cA:false and no keyUsage extension to be used as an intermediate issuer in a chain passed to public_key:pkix_path_validation/3: the cA:false clause recurses into the remaining extensions without rejecting the certificate when it is in issuer position, and the keyUsage check only fires when the extension is present, so a certificate lacking keyUsage entirely bypasses the keyCertSign enforcement. Any party holding an end-entity certificate with basicConstraints cA:false and no keyUsage extension, issued by any CA in the victim's trust store, can use that certificate's private key to sign forged leaf certificates for arbitrary identities. public_key:pkix_path_validation/3 accepts the resulting chain, and by extension every TLS or mTLS endpoint built on the OTP ssl application that relies on the default verifier is affected, including server identity verification on the client side and client certificate verification on mTLS servers. This issue affects OTP from OTP 17.0 before OTP 29.0.1, OTP 28.5.0.1, OTP 27.3.4.12 and OTP 26.2.5.21, corresponding to public_key from 0.22 before 1.21.1, 1.20.3.1, 1.17.1.3 and 1.15.1.7.

Quay 3.9.19