EUVD-2026-83881
GHSA-mhq8-392f-7m6m
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Reachable via the Kubernetes API (AV:N) by an RBAC-granted user (PR:L); AC:H because the non-default checkpoint/restore feature must be enabled and a malicious checkpoint crafted; elevated privileges yield high C/I/A within the node.
Primary rating from Vendor (redhat).
CVSS VectorVendor: redhat
Lifecycle Timeline
4DescriptionCVE.org
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.
AnalysisAI
Elevated-privilege container restoration in CRI-O 1.34 and later, including downstream Red Hat OpenShift Container Platform 4.17+, lets an authenticated Kubernetes user who can create a pod from a crafted checkpoint image bypass the destination pod's security context. The restored process keeps credentials, Linux capabilities, no_new_privs and seccomp state stored in the checkpoint instead of the destination configuration, allowing execution across the container security boundary. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
No credit card · 7-day full trial
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Two concrete prerequisites, both stated in the description: (1) the attacker must have Kubernetes permission to create a pod from a malicious checkpointed container image (an authenticated, RBAC-granted user - PR:L), and (2) CRI-O checkpoint/restore (CRIU) functionality must be available/enabled in the cluster, which is a non-default, opt-in runtime feature. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The vendor CVSS 3.1 score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) rates this High, but the raw score overstates real-world urgency because two hard preconditions gate exploitation: (1) the attacker must already hold Kubernetes RBAC permission to create a pod (PR:L, an authenticated cluster user), and (1) the checkpoint/restore (CRIU) capability must be enabled in the cluster - a non-default, still-maturing feature in CRI-O/OpenShift. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | No vendor-released patch identified at time of analysis: Red Hat states fixes have been applied to supported branches but are not yet released, so the primary action is to track https://access.redhat.com/security/cve/CVE-2026-92574 and https://bugzilla.redhat.com/show_bug.cgi?id=2535436 and apply the fixed CRI-O packages/OCP errata as soon as they ship. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, inventory every cluster running CRI-O 1.34 or later and Red Hat OpenShift Container Platform 4.17 or later, and determine whether checkpoint/restore (CRIU) support is enabled - where the feature is not operationally required, disable it immediately on the affected nodes and restart the container runtime. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
More in Kubernetes
View allA critical vulnerability in Kubernetes ingress-nginx controller allows unauthenticated attackers with pod network access
Credential-harvesting malware compromised 84 versions of 42 TanStack npm packages on 2026-05-11 via chained GitHub Actio
Kubernetes ingress-nginx contains a configuration injection vulnerability via the mirror-target and mirror-host Ingress
A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where the `auth-url` Ingres
A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where the `auth-tls-match-c
Kubernetes API server in all versions allow an attacker who is able to create a ClusterIP service and set the spec.exter
A security issue was discovered in Kubernetes where a user that can create pods on Windows nodes may be able to escalate
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Rated critical severity (CVSS 9.9), this vulne
Unauthenticated remote attackers can trigger complete database overwrites, server-side file reads, and SSRF attacks agai
The Kubernetes integration in GitLab Enterprise Edition 11.x before 11.2.8, 11.3.x before 11.3.9, and 11.4.x before 11.4
Fluentd configuration injection in the kube-logging Logging operator before 6.6.0 allows a namespace-scoped user who can
Kyverno Kubernetes policy engine prior to 1.x has a privilege escalation vulnerability (CVSS 9.9) allowing policy bypass
Same weakness CWE-250 – Execution with Unnecessary Privileges
View allSame technique Privilege Escalation
View allVendor StatusVendor
SUSE
Severity: ImportantShare
External POC / Exploit Code
Leaving vuln.today