Copyright © 2012 Red Hat, Inc. All rights reserved. Important 2026-09-21T00:01:00 cri-o: cri-o: Insufficient validation during container checkpoint restore 8.0 CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H CWE-22

A vulnerability was found in CRI-O related to the container checkpoint and restore feature. When CRI-O is configured to restore containers from checkpoint archives, insufficient validation of restore metadata may allow a user with sufficient privileges to perform unintended operations on the host filesystem. Successful exploitation requires that container checkpoint and restore functionality is enabled, which is not the default configuration. An attacker must also be able to trigger restoration of a container from untrusted checkpoint content.

This issue is classified as Moderate severity for Red Hat OpenShift Container Platform primarily because: 1. Container checkpoint and restore is not enabled by default in CRI-O/OpenShift and requires explicit configuration to be active. 2.Exploitation requires the ability to initiate container restoration using attacker-influenced checkpoint content, which in typical OpenShift deployments implies highly privileged access to node-level interfaces (for example, access associated with kubelet or CRI-O socket operations). 3. While the theoretical impact on an affected node could be significant, the combination of non-default feature enablement and high privilege prerequisites reduces practical exploitability in standard OpenShift hardening models. Until the relevant CRI-O/OpenShift security updates are available, this issue can be mitigated by implementing one or more of the following measures: 1. Do not enable container checkpoint and restore functionality unless it is explicitly required for your environment. 2. Restrict permissions to create workloads and to access node-level container runtime interfaces to trusted administrators only. 3. Do not restore containers from untrusted or unverified checkpoint sources. Red Hat OpenShift Container Platform 4 Affected cri-o https://www.cve.org/CVERecord?id=CVE-2026-15801 https://nvd.nist.gov/vuln/detail/CVE-2026-15801