CVE-2026-92574 Cri-o: cri-o checkpoint restore bypasses destination security context
Attackers with pod creation permissions can bypass security contexts via malicious checkpoints, gaining elevated privileges in CRI-O.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-92574?
CVE-2026-92574 is a high-severity vulnerability in Red Hat Confidential Compute Attestation, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Weakness: CWE-250
Which versions are affected by CVE-2026-92574?
How do I fix CVE-2026-92574?
No fix has been published for CVE-2026-92574 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-92574 being exploited?
There is no known exploitation of CVE-2026-92574 in the wild and no public exploit code.
Sources
Also known as GHSA-mhq8-392f-7m6m.