CVE-2026-91403 is a security vulnerability affecting Oracle Java SE, Oracle GraalVM for JDK, and Oracle GraalVM Enterprise Edition. The vulnerability allows bypassing security restrictions related to intermediate CA certificates from eMudhra. It can be exploited remotely without authentication via network access to the affected Java Secure Socket Extension (JSSE) component. The vulnerability impacts Java deployments that rely on sandboxing, including sandboxed Java Web Start applications and applets running untrusted code. Oracle has released patches for multiple versions to distrust the impacted intermediate CA certificates and recommends updating to the latest Java versions. Red Hat also provides updates for OpenJDK 25 to address related certificate handling issues. Exploitation could lead to high confidentiality and integrity impact but does not affect availability.
Eight intermediate certificate authority (CA) private keys belonging to Indian CA eMudhra Limited were compromised due to insufficient randomness in the certificate generation process. This cryptographic weakness allows attackers to derive private keys from public certificates, enabling unauthorized TLS certificate signing and potential man-in-the-middle (MitM) attacks. Major browser and OS vendors have revoked trust in these intermediates, and eMudhra has revoked the eight compromised certificates. Organizations are advised to audit PKI assets, reissue certificates from trusted CAs, enforce strict revocation checking, and update trust stores to mitigate risk. Palo Alto Networks provides solutions and guidance to assist with managing this incident and preventing exploitation.
Red Hat has issued a security advisory for the grafana-pcp plugin used in Red Hat Enterprise Linux 8. This update addresses multiple vulnerabilities including denial of service issues in golang's crypto/tls and net/http packages, and a man-in-the-middle attack vector via untrusted intermediate certificates in crypto/x509. The vulnerabilities affect the handling of ECH outer extension references, excessive HTTP/2 SETTINGS frames, and certificate validation respectively. The update is rated as Important by Red Hat Product Security and is available for various Red Hat Enterprise Linux 8 architectures and extended life cycle versions.
A vulnerability in Go's crypto/x509 package affects Red Hat Hardened Images RPMs, specifically tempo3.0 version 3.0.4-0.2.hum1. The certificate verification process does not properly block trust in intermediate certificates from compromised Certificate Authorities, allowing a remote attacker to impersonate legitimate servers. This flaw enables man-in-the-middle attacks to intercept or alter secure communications. The issue is rated as important by Red Hat and affects Go-based clients or servers relying on standard certificate verification. Exploitation requires specific network positioning and attacker-controlled certificates. A security update is available from Red Hat to address this vulnerability.
Apache bRPC versions before 1.18.0 have an improper validation of TLS server certificates where the certificate's identity is not bound to the expected DNS name or IP address. This allows a network attacker who can intercept or redirect connections and has a valid certificate for a different name trusted by the client to impersonate the intended TLS endpoint. The issue is fixed in version 1.18.0 by enforcing hostname verification during the TLS handshake.
Improper Certificate Validation vulnerability in Apache Camel Knative component.
This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.
When SSL was enabled on the Knative HTTP client but no truststore was configured, the client options fell back to trusting every presented certificate rather than to the JVM's default trust anchors. A deployment that switched TLS on without also configuring a truststore therefore obtained an encrypted connection with no peer authentication, which an attacker positioned on the network path can terminate and read. The dangerous state is reached by omission rather than by an explicit opt-in, which is what makes it a framework defect: turning TLS on should not be the thing that turns certificate validation off.
Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. With no truststore configured the trust options are now left unset so the JVM default trust anchors apply, the same fallback SSLContextParameters and the rest of Camel use. Trusting every certificate is now reached only by asking for it explicitly through the trust.all property, which remains available for development against a cluster with a self-signed certificate. For deployments that cannot upgrade immediately, configure a truststore explicitly wherever SSL is enabled. After upgrading, a deployment that was relying on the implicit trust-all behaviour must either configure a truststore or set the trust.all property deliberately.
CVE-2024-34459 affects the cert-manager Operator for Red Hat OpenShift, which extends Kubernetes by managing certificate authorities and certificates as first-class resources. The vulnerability involves improper certificate validation due to an oversized Subject Alternative Name (SAN) field, causing fallback to the Common Name (CN) field. This flaw could allow a remote attacker with a man-in-the-middle position and a trusted certificate matching the CN to bypass proper certificate validation, potentially enabling spoofing or interception of communications. The issue impacts TLS clients using GnuTLS on affected Red Hat products but does not affect TLS servers or clients using other cryptographic libraries such as OpenSSL. Red Hat has released version 1.17.2 of the cert-manager Operator to address this vulnerability. Automatic upgrade policies will apply the fix without user intervention; manual approval is required if the upgrade policy is set to manual.
NetEase Cloud Music client for Windows versions 3.1.38 and 3.1.39.205426 have a critical TLS certificate validation vulnerability. The client fails to properly validate the server certificate chain, hostname, and does not consult the Windows certificate trust store. This allows a network-adjacent attacker to perform man-in-the-middle attacks, decrypt HTTPS traffic, capture session credentials, and modify server responses, potentially leading to account takeover and response forgery.
Apache CXF versions prior to 4.2.4, 4.1.9, and 3.6.13 contain a vulnerability in the Netty-based HTTP client transport where the hostname in the server's TLS certificate is not verified against the host being called. This flaw affects both HTTP/1.1 and HTTP/2 connections and allows a network attacker who can intercept traffic to impersonate the target service by presenting any trusted certificate. This can lead to reading or modification of exchanged messages, including credentials. Upgrading to fixed versions is recommended.
FFmpeg versions before 8.1.3 and 9.x before 9.0.2 have a vulnerability in the tls_open() function of libavformat/tls_mbedtls.c that improperly validates certificates by skipping hostname checks for IP-address hosts. This flaw allows network attackers to intercept and tamper with HTTPS, RTMPS, or TLS streams to IP-literal URLs if they present any trusted CA-issued certificate.
A security update for Red Hat Hardened Images RPMs addresses a vulnerability in OpenTelemetry-Go's gRPC log exporter. The flaw allows a network attacker to bypass private Certificate Authority (CA) pinning and mutual TLS configurations due to improper use of system-trusted certificates instead of configured client certificates. This can enable interception and spoofing of the collector connection, potentially leading to unauthorized reading or alteration of sensitive log telemetry data.
Improper Validation of Certificate with Host Mismatch in the C++ and D libraries of Apache Thrift.
Both libraries install a default access manager for client sockets — TSSLSocketFactory does so in C++, and the accessManager property does so in D — which compares the peer certificate against the host
name that was connected to. That comparison walks the subjectAltName dNSName entries first and consults the certificate Common Name afterwards. A name that does not match yields a "skip" result rather than
a rejection, so a certificate whose subjectAltName entries are all present and all non-matching falls through to the Common Name, which can then satisfy the check.
RFC 6125 section 6.4.4, and RFC 9525 section 2, require that the Common Name is not consulted when a dNSName subjectAltName is present. A certificate carrying subjectAltName entries for one name and a
Common Name for another is therefore accepted for a connection to the second name.
Exploitation requires an attacker positioned on the network path who holds a certificate that chains to a certificate authority in the client's trust store and whose Common Name matches the connected host
name. Public certificate authorities have not issued on Common Name alone for many years, so this is principally a concern for deployments using a private or enterprise public-key infrastructure.
This issue affects the C++ library of Apache Thrift from 0.7.0 through 0.24.0 and the D library from 0.9.0 through 0.24.0. Users should upgrade to 0.25.0.
CVE-2026-81871 is a vulnerability in the OpenTelemetry-Go gRPC log exporter used in Red Hat Hardened Images RPMs, specifically the caddy package. The flaw allows a network attacker to bypass private Certificate Authority pinning and mutual TLS configurations due to improper use of system-trusted certificates instead of configured client certificates. This enables interception and spoofing of the collector connection, potentially allowing unauthorized reading or alteration of sensitive log telemetry. Red Hat has released a security update in caddy version 2.11.6-0.1.hum1 to address this issue.