Veille CVE

Recherche « Red Hat OpenShift Container Platform 4.17 »

5 CVE

Critique 1 Élevée 4 Moyenne 0 Faible 0 Non évaluée 0 Exploitées (KEV) Tri : plus récentes « Red Hat OpenShift Container Platform 4.17 » ✕
  1. CVE-2026-75887 7.5 Élevée

    Red Hat OpenShift Container Platform 4.12 · Red Hat OpenShift Container Platform 4.13 · Red Hat OpenShift Container Platform 4.14 · Red Hat OpenShift Container Platform 4.16

    A flaw was found in the OpenShift console. An unauthenticated attacker can exploit a path traversal vulnerability by manipulating the `lng` and `ns` query parameters in the `/locales/resource.json` endpoint. This allows the attacker to read sensitive `*.json` files from the pod filesystem, including plugin manifests and configuration files. Furthermore, this flaw can enable path traversal against registered dynamic-plugin backends.

  2. CVE-2026-75886 7.2 Élevée

    Red Hat OpenShift Container Platform 4.17 · Red Hat OpenShift Container Platform 4.18 · Red Hat OpenShift Container Platform 4.19 · Red Hat OpenShift Container Platform 4.20

    A flaw was found in openshift/console. An unauthenticated remote attacker can exploit a misconfiguration in the CatalogdHandler, which lacks proper authentication, and the forwarding of the `openshift-session-token` cookie. This allows the attacker to send requests to the in-cluster catalogd service, leading to the disclosure of the internal operator-catalog index and providing a relay into the openshift-catalogd namespace.

  3. CVE-2026-92574 8.8 Élevée

    Red Hat Confidential Compute Attestation · Red Hat Enterprise Linux 8 · Red Hat Enterprise Linux 9 · Red Hat OpenShift Container Platform 4

    A vulnerability in CRI-O checkpoint restore allows a user who can create a pod from a malicious checkpointed container to bypass the destination Kubernetes security context. The restored process may retain credentials, Linux capabilities, no_new_privs, and seccomp state from the checkpoint instead of enforcing the destination configuration. This can allow execution with elevated privileges across the container security boundary. Affected upstream supported versions are CRI-O 1.34 and later. Downstream Red Hat products are affected from OCP 4.17 onward. Fixes have been applied to supported branches but are not yet released. Exploitation requires permission to create a pod from a malicious checkpoint image and checkpoint restore functionality to be available.

  4. CVE-2026-75885 9.3 Critique

    Red Hat OpenShift Container Platform 4.12 · Red Hat OpenShift Container Platform 4.13 · Red Hat OpenShift Container Platform 4.14 · Red Hat OpenShift Container Platform 4.16

    A flaw was found in the OpenShift console. Unauthenticated access to the `/api/devfile/` and `/api/devfile/samples/` endpoints allows a remote attacker to send crafted devfile payloads. This can lead to Server-Side Request Forgery (SSRF), where the console pod makes requests to internal services and reflects partial responses to the attacker. Additionally, by sending repeated large requests without a specified content length, an attacker can cause unbounded memory growth, leading to a Denial of Service (DoS).

  5. CVE-2026-31431 7.8 Élevée Exploitée

    Linux · Red Hat NVIDIA for RHEL 10 · Red Hat Enterprise Linux 10 · Red Hat Enterprise Linux 10.0 Extended Update Support

    In the Linux kernel, the following vulnerability has been resolved: crypto: algif_aead - Revert to operating out-of-place This mostly reverts commit 72548b093ee3 except for the copying of the associated data. There is no benefit in operating in-place in algif_aead since the source and destination come from different mappings. Get rid of all the complexity added for in-place operation and just copy the AD directly.