Skip to main content
VulnerabilityPublished Updated

CVE-2026-92574: cri-o · Execution with Unnecessary Privileges

Affects cri-oSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High · fixed in 1.36.6 : patch cri-o soon.

Data as of 5 Nov 2026, 11:40 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (redhat)CVSS 3.18.8
EPSS
0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.36.6, 1.35.9, 1.34.14
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade cri-o to 1.36.6, 1.35.9 or 1.34.14.

Affected software

ProductAffectedFixed in
cri-oAffected
  • >=1.36.0 <1.36.6
Fixed in
  • 1.36.6
cri-oAffected
  • >=1.35.0 <1.35.9
Fixed in
  • 1.35.9
cri-oAffected
  • >=1.34.0 <1.34.14
Fixed in
  • 1.34.14
GitHubcri-opkg:github/cri-oOther threatsAffected
  • >=1.34.0 <1.34.14
  • >=1.35.0 <1.35.9
  • >=1.36.0 <1.36.6
Fixed in
  • 1.34.14
  • 1.35.9
  • 1.36.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in CRI-O versions 1.34.14, 1.35.9, and 1.36.6; users should upgrade to these versions when released. For Red Hat OpenShift Container Platform, apply the corresponding update once available. If you cannot patch yet, mitigate by disabling checkpoint restore if not required (disable the ContainerCheckpoint feature gate in OpenShift or set enable_criu_support = false in crio.conf for standalone CRI-O). Restrict Kubernetes RBAC permissions for pod creation to trusted users only. Enforce Pod Security Standards at the namespace level to limit security contexts. Restrict container image registries to trusted sources to prevent pulling malicious checkpoint images. Identify and remediate any containers restored from untrusted checkpoint images by stopping, deleting, and recreating them.

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.

References

Community reviews

Loading reviews…