CVE-2026-92574Cri-o: cri-o checkpoint restore bypasses destination security context

Description

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.

Timeline

Scores

EPSS (exploitation in 30 days)

0.65% · top 48% of all CVEs (14 Nov 2026)

CISA SSVC

Exploitation: none · Automatable: no · Technical impact: total

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.

Affected products

• cri-o

  • affected 1.34.0 – < 1.34.14
  • affected 1.35.0 – < 1.35.9
  • affected 1.36.0 – < 1.36.6

• Red Hat · Confidential Compute Attestation

  All versions: unaffected

• Red Hat · Red Hat Enterprise Linux 8

  All versions: unaffected

• Red Hat · Red Hat Enterprise Linux 8

  All versions: unaffected

• Red Hat · Red Hat Enterprise Linux 9

  All versions: unaffected

• Red Hat · Red Hat OpenShift Container Platform 4

  All versions: unaffected

• Red Hat · Red Hat OpenShift Container Platform 4

  All versions: affected

• Red Hat · Red Hat OpenShift Container Platform 4

  All versions: unaffected

• Red Hat · Red Hat OpenShift Container Platform 4

  All versions: unaffected

• Red Hat · Red Hat OpenShift Container Platform 4

  All versions: unaffected

• Red Hat · Red Hat OpenShift Container Platform 4

  All versions: unaffected

• Red Hat · Red Hat OpenShift Container Platform 4

  All versions: unaffected

• Red Hat · Red Hat OpenShift Container Platform 4

  All versions: unaffected

• Red Hat · Red Hat OpenShift Container Platform 4

  All versions: unaffected

• Red Hat · Red Hat OpenShift Container Platform 4

  All versions: unaffected

• Red Hat · Red Hat OpenShift Container Platform 5

  All versions: affected

• Red Hat · Red Hat OpenShift Container Platform 5

  All versions: unaffected

• Red Hat · Red Hat OpenShift Container Platform 5

  All versions: unaffected

• Red Hat · Red Hat OpenShift Container Platform 5

  All versions: unaffected

• Red Hat · Red Hat OpenShift Container Platform 5

  All versions: unaffected

• Red Hat · Red Hat OpenShift Container Platform 5

  All versions: unaffected

What to do

Workaround: Upgrade (primary remediation): Update CRI-O to a fixed version once available: 1.36.6 (1.36.x branch), 1.35.9 (1.35.x branch), or 1.34.14 (1.34.x branch). For Red Hat OpenShift Container Platform, apply the corresponding OCP update when released. Until the fix is applied, the following measures reduce exposure: Disable checkpoint restore if not required: In OpenShift, container checkpoint/restore requires the ContainerCheckpoint feature gate, which is Tech Preview and not enabled by default. Clusters that have not explicitly enabled this feature gate are not exposed to this flaw. If it was enabled and is not actively needed, disable it. For standalone CRI-O, set enable_criu_support = false in crio.conf under [crio.runtime] and restart the CRI-O service. Restrict pod creation privileges: Limit Kubernetes RBAC for the create and update verbs on pods, deployments, daemonsets, statefulsets, jobs, and cronjobs resources to trusted users and service accounts only. Exploitation requires the ability to schedule a pod referencing a malicious checkpoint image. Enforce Pod Security Standards: Apply the restricted or baseline Pod Security Standard at the namespace level using Pod Security Admission. While this does not directly block checkpoint restore, it limits the security contexts an attacker can request, reducing the impact if combined with other controls. Restrict container image registries: Use an image policy (e.g., OpenShift image policy, Kyverno, or OPA Gatekeeper) to allowlist trusted registries only. This prevents pods from pulling malicious checkpoint images hosted on attacker-controlled registries. Identify and remediate previously restored containers: If checkpoint restore has been used with images from untrusted sources, stop, delete, and recreate those containers. The restored process state may not match the intended security context.

Sources

The same CVE in the primary databases and aggregators, to check against.

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• EUVD EUVD-2026-83881 (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisories (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

[![CVE-2026-92574](https://cveledger.app/badge/CVE-2026-92574.svg)](https://cveledger.app/cve/CVE-2026-92574)

Record last updated 5 Nov 2026, 00:09 UTC.