CVE-2026-92574

8.8

Kubernetes (CRI-O) / Red Hat · CRI-O / Red Hat OpenShift Container Platform

A vulnerability in CRI-O checkpoint restore allows authenticated users to bypass Kubernetes security contexts, potentially resulting in container processes retaining unauthorized elevated privileges.

Executive summary

A high-severity vulnerability in the CRI-O checkpoint restore functionality allows local authenticated users to execute processes with unintended elevated privileges, posing a significant risk to container isolation.

Vulnerability

This flaw, classified as CWE-250, allows an authenticated user with permission to create pods to bypass security contexts by using a malicious checkpointed container. The restored process improperly retains credentials, Linux capabilities, and seccomp states from the original checkpoint instead of adhering to the destination pod configuration.

Business impact

The exploitation of this vulnerability permits privilege escalation across the container security boundary, which could lead to a full compromise of the containerized environment. Given the CVSS score of 8.8, this flaw represents a significant threat to data confidentiality, system integrity, and service availability, especially within multi-tenant cluster environments where pod isolation is a primary security control.

Remediation

Immediate Action: Monitor official vendor security advisories from Red Hat and the CRI-O project, and prioritize the deployment of security patches as soon as they are released for your specific environment.

Proactive Monitoring: Audit cluster logs for any unauthorized use of the checkpoint and restore functionality, and restrict permissions for creating pods from untrusted container images.

Compensating Controls: Disable checkpoint and restore functionality within the Kubernetes cluster configuration if it is not strictly required for your operational workflows.

Exploitation status

Public Exploit Available: No

Analyst recommendation

This vulnerability presents a severe risk to the integrity of containerized workloads by undermining core security context enforcement mechanisms. Administrators should immediately evaluate their cluster configurations to identify if the checkpoint restore capability is active and restrict access to this feature to highly trusted users. Prepare your deployment pipelines to apply vendor-provided patches immediately upon their release to mitigate the potential for unauthorized privilege escalation.

More Kubernetes (CRI-O) / Red Hat CVEs

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources

Originally found and disclosed by Red Hat would like to thank lyhtheori for reporting this issue., per the CVE Program record.