CVE-2026-92574
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.
How to fix
- cri-o1.34.14, 1.35.9, 1.36.6 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| cri-o | 1.34.0 ≤ v < 1.34.14, 1.35.0 ≤ v < 1.35.9, 1.36.0 ≤ v < 1.36.6 | 1.34.14, 1.35.9, 1.36.6 |
| Red Hat Red Hat OpenShift Container Platform 4 | No range specified | — |
| Red Hat Red Hat OpenShift Container Platform 5 | No range specified | — |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.