CVE-2026-53492
CriticalCVSS 9.6Exploitation Probability (EPSS)
Low risk33th percentile — higher than 33% of all known CVEs
Summary
In containerd versions prior to 2.3.2, 2.2.5 and 2.1.9, the CRI implementation improperly trusts CDI annotations from untrusted checkpoint image metadata during container restoration. A user with pod creation permissions can bypass standard Kubernetes resource allocation and inject arbitrary devices or host mounts into the restored container.
Risk Assessment
The risk involves privilege escalation and container isolation bypass, potentially leading to unauthorized host resource access and full node compromise in Kubernetes environments.
Recommendation
Upgrade containerd to versions 2.3.2, 2.2.5 or 2.1.9 immediately. If upgrading is not feasible, consider disabling CDI on nodes where it is not required.
Original NVD description (English source)
containerd is an open-source container runtime. In Versions prior to 2.3.2, 2.2.5 and 2.1.9, the CRI implementation improperly trusts Container Device Interface (CDI) annotations found within untrusted checkpoint image metadata during container restoration. When restoring a container from a checkpoint, containerd preserves CDI-related annotations from the checkpoint archive rather than relying solely on the pod's create-time specification. This allows a user with pod creation permissions to bypass standard Kubernetes resource allocation and device plugin enforcement, injecting arbitrary CDI edits (such as device nodes and host mounts) into the restored container. Successful exploitation requires that the node has CDI enabled and contains a matching host CDI specification for the requested device; environments where CDI is disabled or lacking sensitive device specifications are not affected. This issue has been fixed in versions 2.3.2, 2.2.5 and 2.1.9.