Veille CVE

Recherche « Red Hat OpenShift Serverless »

3 CVE

Critique 0 Élevée 1 Moyenne 2 Faible 0 Non évaluée 0 Exploitées (KEV) Tri : plus récentes « Red Hat OpenShift Serverless » ✕
  1. CVE-2026-114406 6.8 Moyenne

    Red Hat Hardened Images · Red Hat Assisted Installer for Red Hat OpenShift Container Platform 2 · Red Hat cert-manager Operator for Red Hat OpenShift · Red Hat Confidential Compute Attestation

    The system certificate authority (CA) store in Red Hat products, distributed via ca-certificates RPM packages, included multiple root CA certificates of authorities, which signed intermediate CA certificates with weak private keys issued by the eMudhra certificate authority. A man-in-the-middle attacker could use this flaw to issue certificates for arbitrary host names signed by the weak intermediate CA certificates, which would be considered trusted by a TLS/SSL client using system CA store and cause such clients to connect to malicious sites. Due to inability to only distrust specific intermediate certificates in all clients using the system CA store, root CA certificates of authorities that signed weak intermediate CA certificates are being removed.

  2. CVE-2026-107174 6.4 Moyenne

    Red Hat OpenShift Serverless · Red Hat OpenShift Source-to-Image (S2I) · Red Hat OpenShift Container Platform 4 · Red Hat Web Terminal

    A flaw was found in source-to-image. When unpacking archive files, the application fails to properly sanitize symbolic links pointing to absolute file paths. An attacker who supplies a malicious builder image can exploit this vulnerability by embedding links pointing outside the extraction directory. This allows the attacker to bypass sandbox boundaries, potentially leading to unauthorized information disclosure or file modification on the host system.

  3. CVE-2026-87743 7.5 Élevée

    Red Hat build of Quarkus 3.27.5.SP2 · Red Hat build of Quarkus 3.33.3.SP2 · Red Hat Exploit Intelligence · Red Hat OpenShift Serverless

    A flaw was found in Quarkus HTTP security. An unauthenticated attacker can exploit a discrepancy in how paths are normalized between the security matcher and HTTP request dispatchers. This allows the attacker to craft a URL that the security matcher considers public, but which is then routed to a protected endpoint, leading to an authorization bypass and potential unauthorized access to sensitive information.