CVE-2026-53492: containerd CRI checkpoint restore CDI annotation smuggling
Impact containerd's 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.
Published Jun 19, 2026
Affected packages
github.com/containerd/containerd/v2
- Ecosystem
- Go
- Affected
- >= 2.1.0, < 2.1.9
- Fixed in
- 2.1.9
- Check
go list -m github.com/containerd/containerd/v2
github.com/containerd/containerd/v2
- Ecosystem
- Go
- Affected
- >= 2.2.0, < 2.2.5
- Fixed in
- 2.2.5
- Check
go list -m github.com/containerd/containerd/v2
github.com/containerd/containerd/v2
- Ecosystem
- Go
- Affected
- >= 2.3.0, < 2.3.2
- Fixed in
- 2.3.2
- Check
go list -m github.com/containerd/containerd/v2
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
containerd's 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.
Patches
This bug has been fixed in the following containerd versions:
- 2.3.2
- 2.2.5
- 2.1.9
Users should update to these versions to resolve the issue. Recreating existing containers restored from untrusted checkpoints may be necessary to remove smuggled configuration.
Workarounds
Users can mitigate this issue by restricting the restoration of containers from untrusted checkpoint images. If Container Device Interface (CDI) capabilities are not utilized on the node, removing or temporarily relocating host CDI specifications from the default directories (/etc/cdi and /var/run/cdi) will eliminate the reachability of this vulnerability.
Credits
The containerd project would like to thank Robert Prast (@robertprast) for responsibly disclosing this issue in accordance with the containerd security policy.
For more information
If you have any questions or comments about this advisory:
- Open an issue in containerd
- Email us at [[email protected]](mailto:[email protected])
To report a security issue in containerd:
- Report a new vulnerability
- Email us at [[email protected]](mailto:[email protected])
Credited to robertprast.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-95839
containerd image-triggered daemon crash via malformed digest in subject-annotated descriptor
high7.1Nov 19, 2026CVE-2026-95837
containerd CRI plugin: Checkpoint restore bypasses destination security context
high7.8Oct 15, 2026CVE-2026-95838
containerd: Unpack DoS via repeated opaque whiteouts
medium4.6Oct 15, 2026CVE-2026-53493
Containerd has image-pull DoS via crafted OCI index graph amplification
medium6.9Sep 25, 2026CVE-2026-53495
containerd: CRI ExecSync Goroutine Leak Leads to Node-Level Denial of Service
medium6.8Sep 9, 2026CVE-2026-47262
containerd image-triggered runtime DoS via unbounded group parsing
medium6.9Jun 19, 2026
