Skip to content
Fencer Vulns
high 8.8

CVE-2026-92574 json

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

published 2026-09-21 49 d ago modified 2026-11-05 4 d ago also EUVD-2026-83881

cvss
8.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 51%
public exploits
0
none known

Summary

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.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-92574 updated cvss 8.8

cri-o: CRI-O checkpoint restore bypasses destination security context

  • Red Hat OpenShift Container Platform 4 cri-o Red Hat OpenShift Container Platform 5 cri-o
    affected: workaround, no fix available
  • Red Hat Confidential Compute Attestation openshift-sandboxed-containers/osc-monitor-rhel9
    not affected: vulnerable code not in execute path
  • Red Hat Enterprise Linux 8 conmon, podman, podman-tests, podman-docker, podman-remote, podman-gvproxy, +3 more Red Hat Enterprise Linux 9 conmon Red Hat OpenShift Container Platform 4 conmon, kata-containers, openshift4/cnf-tests-rhel8, openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9, ose-crio-credential-provider, +3 more
    not affected: vulnerable code not present
  • Red Hat OpenShift Container Platform 5 kata-containers, openshift/ose-rhel-coreos-9, ose-crio-credential-provider, openshift5/microshift-bootc-rhel9, openshift5/microshift-bootc-rhel10
    not affected: vulnerable code not in execute path

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
48 d ago

Exploit prediction

0.65% chance of exploitation in the next 30 days, higher than 51% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Red Hat Confidential Compute Attestation
  • Red Hat Red Hat Enterprise Linux 8
  • Red Hat Red Hat Enterprise Linux 9
  • Red Hat Red Hat OpenShift Container Platform 4
  • Red Hat Red Hat OpenShift Container Platform 5

Classification

Weakness
  • CWE-250 Execution with Unnecessary Privileges

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.