Database/Container, Kubernetes & orchestration
CRI-O: restoring a malicious checkpoint keeps the source security context and bypasses pod policy
Impact
A tenant who can create a pod from a checkpoint image they control gets a process that keeps the credentials, Linux capabilities, no_new_privs flag and seccomp state baked into the checkpoint instead of the ones the destination pod spec asks for. On a shared GPU cluster that is a direct escape from the security context an operator thought it was enforcing: the restored container can run with capabilities and a seccomp profile that admission policy would never have admitted, on a node that also hosts other tenants' GPU workloads. Red Hat scores it 8.8 with confidentiality, integrity and availability all high. CRI-O 1.34 and later are affected upstream; downstream OpenShift from 4.17 onward.
Who can reach it
An authenticated cluster user with permission to create a pod, on a cluster where CRI-O checkpoint/restore is enabled, who can supply a checkpoint image of their choosing. No node access and no host foothold needed.
What to do
No fixed release exists yet - Red Hat states the fixes are merged to supported branches but not shipped. Until a build lands, the practical mitigation is to turn off checkpoint/restore support in CRI-O (it is not enabled by default in every distribution) and to restrict who may create pods from checkpoint images, for example by admission policy on the image source. Both are configuration changes; disabling the feature means editing the CRI-O config and restarting the runtime on each node, which evicts the pods on that node.
References
Related entries
- Arcane: delegated users:update permission lets any operator reset the global administrator passwordCVE-2026-96627 · Arcane Docker management UI (UpdateUser in backend/api/handlers/users.go)High
- KubeVirt: Path traversal lets a user who can configure KubeVirt read arbitrary host filesCVE-2022-1798 · KubeVirtHigh
- BuildKit: Race between parallel build steps sharing cache mounts with subpathsCVE-2024-23651 · BuildKitHigh
- Sonatype Nexus Repository: weak format-specific API key generation lets a remote attacker act as a targeted userCVE-2026-11403 · Sonatype Nexus Repository Manager (format-specific API key generation: Docker Bearer Token, npm, NuGet)High
- Kyverno: unchecked type assertion in shallow variable substitution panics the policy engineCVE-2026-122314 · Kyverno admission controller (variable-substitution engine, shallow `{{- var }}` substitution)High
- Kyverno: non-string attestation `type` field panics image verification, bypassing signature checksCVE-2026-122315 · Kyverno image verification (buildStatementMap attestation statement parsing)High
This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.