# CVE-2026-92574: Cri-o: cri-o checkpoint restore bypasses destination security context

> Attackers with pod creation permissions can bypass security contexts via malicious checkpoints, gaining elevated privileges in CRI-O.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Sep 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-mhq8-392f-7m6m

## What is CVE-2026-92574?

CVE-2026-92574 is a high-severity vulnerability in Red Hat Confidential Compute Attestation, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-250 (Execution with Unnecessary Privileges)

## Which versions are affected by CVE-2026-92574?


## How do I fix CVE-2026-92574?

No fix has been published for CVE-2026-92574 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-92574 being exploited?

There is no known exploitation of CVE-2026-92574 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92574 and fix it if it is affected.

What it is: CVE-2026-92574 is a high-severity vulnerability in Red Hat Confidential Compute Attestation, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92574 in the wild and no public exploit code.

Affected product: Red Hat Confidential Compute Attestation. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92574/ (Markdown: https://insights.sbomify.com/CVE-2026-92574/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92574
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92574
- OSV: https://osv.dev/vulnerability/CVE-2026-92574

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92574/
Summaries are generated and may contain mistakes; the official description above is the record.