CVE-2026-92574
Cri-o: cri-o checkpoint restore bypasses destination security context
What happened?
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.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| cri-o | affected: 1.34.0 to < 1.34.14; affected: 1.35.0 to < 1.35.9; affected: 1.36.0 to < 1.36.6 | See vendor advisory |
| openshift-sandboxed-containers/osc-monitor-rhel9Red Hat | Default status: unaffected | See vendor advisory |
| container-tools:rhel8/conmonRed Hat | Default status: unaffected | See vendor advisory |
| container-tools:rhel8/podmanRed Hat | Default status: unaffected | See vendor advisory |
| conmonRed Hat | Default status: unaffected | See vendor advisory |
| conmonRed Hat | Default status: unaffected | See vendor advisory |
| cri-oRed Hat | Default status: affected | See vendor advisory |
| kata-containersRed Hat | Default status: unaffected | See vendor advisory |
| openshift4/cnf-tests-rhel8Red Hat | Default status: unaffected | See vendor advisory |
| openshift4/microshift-bootc-rhel10Red Hat | Default status: unaffected | See vendor advisory |
| openshift4/microshift-bootc-rhel9Red Hat | Default status: unaffected | See vendor advisory |
| openshift4/ztp-site-generate-rhel8Red Hat | Default status: unaffected | See vendor advisory |
| openshift/ose-rhel-coreos-8Red Hat | Default status: unaffected | See vendor advisory |
| openshift/ose-rhel-coreos-9Red Hat | Default status: unaffected | See vendor advisory |
| ose-crio-credential-providerRed Hat | Default status: unaffected | See vendor advisory |
| cri-oRed Hat | Default status: affected | See vendor advisory |
| kata-containersRed Hat | Default status: unaffected | See vendor advisory |
| openshift5/microshift-bootc-rhel10Red Hat | Default status: unaffected | See vendor advisory |
| openshift5/microshift-bootc-rhel9Red Hat | Default status: unaffected | See vendor advisory |
| openshift/ose-rhel-coreos-9Red Hat | Default status: unaffected | See vendor advisory |
| ose-crio-credential-providerRed Hat | Default status: unaffected | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.