Export
The link always opens the latest version of this page.
Ask an AI about it
Open in ChatGPTA new chat that reads this entry from the site Open in ClaudeThe same, in ClaudeShare the link instead of a file, and they will always see the latest version.
Files are a snapshot of today. The live page has anything newer.
CVE-2026-92574
CRI-O checkpoint restore can bypass Kubernetes security policies by preserving older process privileges and credentials
- Weakness
- Privilege Escalation 1 source
- Disclosed
- 2026 1 source
A vulnerability in CRI-O checkpoint and restore functionality that allows bypassing Kubernetes security policies by preserving process privileges and credentials from earlier execution states.
Affected Products
CRI-O1 and OpenShift Container Platform1 are vulnerable to this issue.
Technical Details
The vulnerability exists in the checkpoint-restore mechanism, which enables containers to be paused, saved to disk, and later resumed. During restoration, the process retains privileges and credentials from the checkpoint state rather than applying current security policies. This allows an attacker to restore a container to a state with elevated privileges that would not be permitted under the current RBAC or Pod Security Policy configuration.
Impact
This constitutes a privilege escalation vulnerability1, enabling containers to operate with permissions beyond what security policies should allow. An attacker with the ability to create or restore checkpoints could bypass admission controllers and runtime security enforcement.
Remediation
A patch is available1 for affected versions. Users should update CRI-O and OpenShift Container Platform to patched releases. Additionally, restricting checkpoint and restore operations through RBAC policies can limit exposure until patches are applied.
References
Facts 3
| Attribute | Value | Confidence | Sources | Cited |
|---|---|---|---|---|
| Weakness | Privilege Escalation | low | 1 | 1 |
| Disclosed | 2026 | low | 1 | 1 |
| Patch status | patch-available | low | 1 | 1 |
Affected product 3
Neighbourhood
Affects 2
Frequently mentioned together 8
Sources 5
- CRI-O Restore Flaw Can Bypass Kubernetes Security Policies · LinuxSecurity: Articles
- Why Seccomp Must Be Rechecked After Container Restore · LinuxSecurity: Articles
- How Container Restore Can Reopen Privilege Escalation Paths · LinuxSecurity: Articles
- What CRIU Restores Beyond Application Memory in Linux Containers · LinuxSecurity: Articles
- Why Container Security Needs a Separate Restore Boundary · LinuxSecurity: Articles