cve.bz

CVE-2026-92574 Execution with Unnecessary Privileges

8.8 highEPSS 0.7%

High (8.8). EPSS 0.7% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 52nd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-09-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-250 Execution with Unnecessary Privileges
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-92574 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-92574?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-92574?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-92574 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Red Hat

Red Hat rates this Important.

Red Hat's statement

A flaw was found in CRI-O's checkpoint restore implementation. When restoring a container from a checkpoint archive or annotated OCI image pulled from a remote registry, CRIU restores process credentials, Linux capabilities, the no_new_privs bit, and seccomp state directly from the checkpoint data rather than enforcing the security context specified in the Kubernetes pod specification. An attacker with pod creation privileges can craft a malicious checkpointed container image that, when restored, executes processes as root with full capabilities and no seccomp filtering, bypassing the security policies requested by the orchestrator. CRI-O's checkpoint restore from remote registries is enabled by default in affected versions, making this exploitable without local node access.

Red Hat's mitigation

Upgrade (primary remediation): Update CRI-O to a fixed version once available: 1.36.6 (1.36.x branch), 1.35.9 (1.35.x branch), or 1.34.14 (1.34.x branch). For Red Hat OpenShift Container Platform, apply the corresponding OCP update when released.

Until the fix is applied, the following measures reduce exposure:

Disable checkpoint restore if not required: In OpenShift, container checkpoint/restore requires the ContainerCheckpoint feature gate, which is Tech Preview and not enabled by default. Clusters that have not explicitly enabled this feature gate are not exposed to this flaw. If it was enabled and is not actively needed, disable it. For standalone CRI-O, set enable_criu_support = false in crio.conf under [crio.runtime] and restart the CRI-O service.

Restrict pod creation privileges: Limit Kubernetes RBAC for the create and update verbs on pods, deployments, daemonsets, statefulsets, jobs, and cronjobs resources to trusted users and service accounts only. Exploitation requires the ability to schedule a pod referencing a malicious checkpoint image.

Enforce Pod Security Standards: Apply the restricted or baseline Pod Security Standard at the namespace level using Pod Security Admission. While this does not directly block checkpoint restore, it limits the security contexts an attacker can request, reducing the impact if combined with other controls.

Restrict container image registries: Use an image policy (e.g., OpenShift image policy, Kyverno, or OPA Gatekeeper) to allowlist trusted registries only. This prevents pods from pulling malicious checkpoint images hosted on attacker-controlled registries.

Identify and remediate previously restored containers: If checkpoint restore has been used with images from untrusted sources, stop, delete, and recreate those containers. The restored process state may not match the intended security context.

ProductPackageStateAdvisory
Confidential Compute Attestationopenshift-sandboxed-containers/osc-monitor-rhel9Not affected
Red Hat Enterprise Linux 8container-tools:rhel8/conmonNot affected
Red Hat Enterprise Linux 8container-tools:rhel8/podmanNot affected
Red Hat Enterprise Linux 9conmonNot affected
Red Hat OpenShift Container Platform 4conmonNot affected
Red Hat OpenShift Container Platform 4cri-oAffected
Red Hat OpenShift Container Platform 4kata-containersNot affected
Red Hat OpenShift Container Platform 4openshift4/cnf-tests-rhel8Not affected
Red Hat OpenShift Container Platform 4openshift4/microshift-bootc-rhel10Not affected
Red Hat OpenShift Container Platform 4openshift4/microshift-bootc-rhel9Not affected
Red Hat OpenShift Container Platform 4openshift4/ztp-site-generate-rhel8Not affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Not affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Not affected
Red Hat OpenShift Container Platform 4ose-crio-credential-providerNot affected
Red Hat OpenShift Container Platform 5cri-oAffected
Red Hat OpenShift Container Platform 5kata-containersNot affected
Red Hat OpenShift Container Platform 5openshift5/microshift-bootc-rhel10Not affected
Red Hat OpenShift Container Platform 5openshift5/microshift-bootc-rhel9Not affected
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Not affected
Red Hat OpenShift Container Platform 5ose-crio-credential-providerNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-92574.

Attack patterns (CAPEC)

  • CAPEC-69 Target Programs with Elevated Privileges Likelihood: High · Severity: Very High
  • CAPEC-104 Cross Zone Scripting Likelihood: Medium · Severity: High
  • CAPEC-470 Expanding Control over the Operating System from the Database Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON