Affects widely used container runtime (CRI-O) and Red Hat OpenShift; enables privilege escalation across container boundary—impacting many Kubernetes deployments.
CVE-2026-92574
CRI-O checkpoint restore may retain elevated privileges across containers.
Is CVE-2026-92574 being exploited?
Not confirmed. CVE-2026-92574 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.
How severe is CVE-2026-92574?
CVE-2026-92574 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-92574?
Not known from our data. No patch reference has been recorded for CVE-2026-92574, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-92574 affect?
CVE-2026-92574 affects CRI-O 1.34+, Red Hat OpenShift Container Platform 4.17+, Kubernetes clusters using CRI-O. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-92574?
Prevent untrusted checkpoint restores; restrict pod creation rights; apply vendor patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Privilege escalation: restored processes can retain credentials, Linux capabilities, no_new_privs, and seccomp state, enabling elevated execution across container boundary.
Immediate action required