Skip to content
major vulnerability· requires attention

Affects widely used container runtime (CRI-O) and Red Hat OpenShift; enables privilege escalation across container boundary—impacting many Kubernetes deployments.

Cloud

CVE-2026-92574

8.8
High
EPSS 0.65%

CRI-O checkpoint restore may retain elevated privileges across containers.

exploited
No known exploitation not in CISA KEV as of our last sync
fix
No fixed release stated by the publisher
likelihood
EPSS 0.65%top 49% of scored CVEs
Published 21 Sept 2026Analysed here 21 Sept 2026CVSS scored by the publisher (CNA)
common questions

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. EPSS currently estimates a 0.65% probability of exploitation in the next 30 days.

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.

executive summary
technical analysis
affected
CRI-O 1.34+Red Hat OpenShift Container Platform 4.17+Kubernetes clusters using CRI-O
impact

Privilege escalation: restored processes can retain credentials, Linux capabilities, no_new_privs, and seccomp state, enabling elevated execution across container boundary.

action required

Immediate action required

cisa ssvc

exploitation
none
automatable
no
technical impact
total

Assessed by CISA 21 Sept 2026 (SSVC 2.0.3).

timeline

  1. 21 Sept 2026Published
  2. 21 Sept 2026Analysed by vulneraibility.com · same day later
  3. 21 Sept 2026CISA SSVC assessment: exploitation none · same day later
  4. 30 Oct 2026CVE record last updated · 39 days later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
2 references in the CVE record: 2 links

sources

  • CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
  • NVD: CVSS and CPE data
  • CISA Vulnrichment (ADP): SSVC decision points
  • FIRST EPSS: exploit probability and percentile
  • Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved