Vulnerability Description
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.
CVSS Score
CRITICAL
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Linuxfoundation | Containerd | >= 2.1.0, < 2.1.9 |
Related Weaknesses (CWE)
References
- https://github.com/containerd/containerd/security/advisories/GHSA-33vj-92qq-66hcMitigationVendor Advisory
FAQ
What is CVE-2026-53492?
CVE-2026-53492 is a vulnerability with a CVSS score of 9.6 (CRITICAL). 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 untruste...
How severe is CVE-2026-53492?
CVE-2026-53492 has been rated CRITICAL with a CVSS base score of 9.6/10. This is considered a critical vulnerability requiring immediate attention.
Is there a patch for CVE-2026-53492?
Check the references section above for vendor advisories and patch information. Affected products include: Linuxfoundation Containerd.