The Quarterly Threat Landscape Report is out. See what attackers are targeting now.Read report
A vulnerability was found in CRI-O, where it can be requested to take a checkpoint archive of a container and later be asked to restore it. When it does that restoration, it attempts to restore the mounts from the restore archive instead of the pod request. As a result, the validations run on the pod spec, verifying that the pod has access to the mounts it specifies are not applicable to a restored container. This flaw allows a malicious user to trick CRI-O into restoring a pod that doesn't have access to host mounts. The user needs access to the kubelet or cri-o socket to call the restore endpoint and trigger the restore.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Redhat Openshift | — | Upgrade ose-rhel-coreosUpgrade cri-o | Dec 16, 2024 | Nov 26, 2024 |
| Redhat_linux | — | No solution exists | Jul 9, 2025 | Nov 26, 2024 |
| Suse | — | Upgrade govulncheck-vulndb | Dec 5, 2025 | Dec 12, 2024 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub