CVE-2026-53492: containerd CRI Annotation Smuggling Vulnerability
Summary
CVE-2026-53492: containerd CRI checkpoint restore CDI annotation smuggling. Affects github.com/containerd/containerd/v2 across 3 version ranges.
>= 2.1.0, < 2.1.9
>= 2.2.0, < 2.2.5
>= 2.3.0, < 2.3.2
Fixed in 2.1.9, 2.2.5 or 2.3.2, depending on the release line you run. How to fix ↓
Also tracked for
The same CVE-2026-53492 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
containerd is an industry-standard core container runtime that manages the complete lifecycle of containers. It provides functionalities such as image transfer, storage, and execution of containers. The containerd CRI (Container Runtime Interface) enables Kubernetes to interact with containerd, allowing for efficient container management. However, a vulnerability exists in its handling of Container Device Interface (CDI) annotations during the restoration of containers from untrusted checkpoints, which could lead to unauthorized access and resource manipulation.
Vulnerability Detail
The vulnerability arises from containerd's improper trust in CDI annotations found in untrusted checkpoint image metadata. When restoring a container, containerd retains CDI-related annotations from the checkpoint archive instead of relying solely on the pod's create-time specifications. This flaw allows users with pod creation permissions to bypass Kubernetes resource allocation and device plugin enforcement, injecting arbitrary CDI edits into the restored container. Successful exploitation requires that CDI is enabled on the node and that there is a matching host CDI specification for the requested device. Environments without CDI or sensitive device specifications are not affected.
How To Fix
Latest published version: v2.4.2 as of 23 Oct 2026
go get github.com/containerd/containerd/v2@v2.4.2
Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
>= 2.1.0, < 2.1.92.1.9go get github.com/containerd/containerd/v2@v2.1.9 -
>= 2.2.0, < 2.2.52.2.5go get github.com/containerd/containerd/v2@v2.2.5 -
>= 2.3.0, < 2.3.22.3.2go get github.com/containerd/containerd/v2@v2.3.2
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
Users can mitigate the issue by restricting the restoration of containers from untrusted checkpoint images. If CDI capabilities are not utilized on the node, it is recommended to remove or temporarily relocate host CDI specifications from the default directories: /etc/cdi and /var/run/cdi.
Conclusion
CVE-2026-53492 represents a significant vulnerability in containerd's handling of CDI annotations during container restoration. Users are strongly advised to update to the latest patched versions and implement the recommended workarounds to mitigate potential risks. Regular monitoring for vulnerabilities using tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for github.com/containerd/containerd/v2 →
FAQ
CVE-2026-53492 is a vulnerability in containerd's CRI implementation that allows unauthorized manipulation of container configurations through CDI annotation smuggling.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.
The vulnerability can lead to unauthorized access to resources and manipulation of container configurations, which may compromise the security and stability of the application.
You can update containerd by using your package manager or downloading the latest version from the official containerd repository. Ensure you choose one of the patched versions: 2.3.2, 2.2.5, or 2.1.9.
The CVSS score of CVE-2026-53492 is 8.4, indicating a high severity level.
References
Related vulnerabilities
Recent vulnerabilities recorded for github.com/containerd/containerd/v2.