CVE-2026-92574

published 21 Sep 2026 · updated 5 Nov 2026

Cri-o: cri-o checkpoint restore bypasses destination security context

8.8HighCVSS 8.8EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 1.34.14, 1.35.9 and 1.36.6.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
Red HatConfidential Compute Attestation
Red HatEnterprise Linux
Red HatOpenShift Container Platform
>=1.34.0 <1.34.14, >=1.35.0 <1.35.9, >=1.36.0 <1.36.61.34.14, 1.35.9, 1.36.6

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Red Hat, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-92574 severity on Zeptric[![CVE-2026-92574](https://zeptric.io/badge/cve/CVE-2026-92574.svg)](https://zeptric.io/cve/CVE-2026-92574)