Loading vulnerability…
CVE-2026-92574 is a security-context bypass in CRI-O checkpoint restoration. When CRI-O restores an attacker-controlled checkpointed container into a Kubernetes pod, it may preserve the source process's credentials, Linux capability sets, no_new_privs state, and seccomp state rather than enforcing the destination pod's requested security context. This creates a discrepancy between the pod configuration accepted by Kubernetes and the effective security attributes enforced for the restored process. The issue affects supported upstream CRI-O 1.34 and later, and Red Hat OpenShift Container Platform 4.17 and later where checkpoint restore is available.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A CRI-O checkpoint-restore flaw in which restored process security state, including seccomp and no_new_privs, may be retained from checkpoint data rather than enforcing the destination Kubernetes security context. A malicious checkpoint can therefore cause the effective syscall restrictions to differ from the pod's declared policy.
A privilege-escalation vulnerability in CRI-O checkpoint restore handling where a malicious checkpoint may restore saved credentials and Linux capabilities rather than enforce the destination Kubernetes pod security configuration.
A CRI-O checkpoint/restore policy-enforcement flaw in which a malicious CRIU checkpoint can preserve source-process credentials, Linux capabilities, no_new_privs, and seccomp state rather than enforcing the destination Kubernetes security context, potentially restoring privileges that destination administrators intended to remove.
A CRI-O container-checkpoint restore vulnerability in which a malicious checkpoint can cause saved Linux process security state to override the destination pod's requested security policy.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.