CRI-O Checkpoint Restore Bypasses Kubernetes Security Context

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.

Casky was already ahead

This CVE exploits attack patterns that Casky's 224matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

CVE-2026-92574 exploits a critical flaw in CRI-O's checkpoint restore functionality that allows attackers to circumvent Kubernetes security contexts when restoring containers from malicious checkpoints. When a pod is created from a compromised checkpoint, the restored process inherits its original security posture—including credentials, Linux capabilities, no_new_privs settings, and seccomp policies—rather than adopting the destination environment's security configuration. This means an attacker who can supply a crafted checkpoint can execute code with elevated privileges that the destination pod's security policy explicitly denies, effectively breaking the container isolation boundary. CRI-O versions 1.34 and later are affected, impacting any organization relying on checkpoint/restore for container management, disaster recovery, or live migration scenarios.

Casky's 224 matched security skills map directly to MITRE ATT&CK technique TA0004 (Privilege Escalation), enabling detection of the attack patterns underlying this vulnerability. Practitioners using Casky's Claude AI-powered analysis will identify suspicious indicators such as: processes spawning with unexpected elevated capabilities that contradict pod security policies, credential artifacts appearing in restored containers that weren't explicitly provisioned, seccomp bypass attempts originating from checkpoint sources, and no_new_privs flag violations. The platform's extended reasoning capability correlates these signals across container lifecycle events—checkpoint creation, tampering, and restoration—to surface the mismatch between intended and actual security contexts. Security teams will receive findings highlighting unauthorized privilege retention, lateral movement opportunities from restored containers, and evidence of security boundary violations that conventional pod inspection tools might miss.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

224 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-92574.

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

Access with Stolen Session Cookie

identity access management · low

Run

MITRE ATT&CK Techniques

TA0004

Investigate the attack patterns behind CVE-2026-92574

Casky has 224 skills that investigate the attack patterns behind CVE-2026-92574. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn