CRI-O EUVD-2026-83865

Exploitation requires that CRI-O's container checkpoint and restore (C/R) feature is explicitly enabled - this is NOT the default configuration. The attacker must additionally hold sufficient privileges to trigger restoration of a container (PR:H) and must be able to supply or influence untrusted checkpoint archive content whose restore metadata is parsed by CRI-O. Limiting factors: non-default feature gate, required elevated/restore privileges, and dependence on the ability to inject a malicious checkpoint archive into the restore path - together these substantially narrow the exploitable population beyond the raw 8.0 score.

The vendor CVSS 3.1 base score is 8.0 (AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H), driven high by full C/I/A impact and a scope change from container to host. However, two metrics substantially temper real-world risk: PR:H (attacker must already hold sufficient privileges to trigger a container restore) and AC:H (exploitation depends on the non-default checkpoint/restore feature being enabled and the attacker being able to feed untrusted checkpoint content). No EPSS score, no CISA KEV listing, and no public exploit code were provided in the intelligence - so this is 'no public exploit identified at time of analysis.' The AV:N assignment is debatable: checkpoint archives are frequently pulled from a registry/network source, which supports AV:N, but if restoration is a purely local/administrative operation the vector could be closer to AV:L - verify the delivery path with Red Hat. Net assessment: a genuine host-escape/path-traversal flaw with serious technical impact, but its exploitability is heavily gated by non-default configuration and required privileges, so it is a high-severity-but-conditional issue rather than a broadly wormable priority. Prioritize only for clusters that have explicitly enabled container checkpoint/restore.

An operator or workload with restore privileges in an OpenShift/CRI-O cluster that has enabled container checkpoint/restore triggers restoration of a container from an attacker-supplied checkpoint archive. Crafted restore metadata containing path-traversal sequences causes CRI-O to write to or manipulate host filesystem paths outside the intended container scope, breaking container isolation (S:C) and potentially compromising the node. No public proof-of-concept was identified in the provided data.