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.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 1
- First seenCVSS 8.8 · red hatNVD modified 2026-10-30 05:04
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 2
- https://access.redhat.com/security/cve/CVE-2026-92574 vdb-entry, x_refsource_redhat
- https://bugzilla.redhat.com/show_bug.cgi?id=2535436 issue-tracking, x_refsource_redhat