CVE-2026-50195: containerd CRI Checkpoint Import Vulnerability Leading to Image Tag Poisoning
Summary
CVE-2026-50195: containerd: CRI checkpoint import allows local image tag poisoning. 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-50195 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 container lifecycle, including image transfer, storage, and execution. It is widely used in cloud-native environments and is integral to Kubernetes. However, a vulnerability in its CRI checkpoint import process has been identified, which allows an attacker to manipulate image references, potentially compromising the security of the node and its pods.
Vulnerability Detail
The vulnerability arises from containerd's failure to validate image references within a checkpoint image's configuration. An attacker with permissions to create pods can craft a malicious checkpoint image that forces containerd to pull a harmful image and assign it an arbitrary local tag. This leads to the poisoning of the node's local image cache. Consequently, if other pods on the same node use the poisoned tag with an 'IfNotPresent' or 'Never' pull policy, they may inadvertently execute the attacker's malicious image, resulting in a compromise of the affected pods and allowing the attacker to execute arbitrary code under the victim pod's identity.
How To Fix
Latest published version: v2.4.2 as of 23 Oct 2026
go get github.com/containerd/containerd/v2@v2.4.2Upgrading 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
As a temporary measure, users should restrict the pulling of images to only trusted sources to mitigate the risk of using a poisoned image tag.
Conclusion
In summary, the vulnerability identified as CVE-2026-50195 in containerd's CRI checkpoint import process poses a significant risk by allowing image tag poisoning. Users are strongly advised to update to the patched versions to secure their environments and mitigate potential attacks.
See every vulnerability recorded for github.com/containerd/containerd/v2 →
FAQ
The CVSS score for this vulnerability is 5.6, indicating a moderate level of risk.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
Failure to address this vulnerability may lead to the execution of malicious code within your pods, compromising the security and integrity of your applications.
The vulnerability was independently discovered and responsibly disclosed by Henry Beberman from Microsoft and the GKE Security Team, among others.
If immediate updates are not possible, ensure that only trusted images are allowed to be pulled to minimize the risk of exploitation.
References
Related vulnerabilities
Recent vulnerabilities recorded for github.com/containerd/containerd/v2.
