CVE-2026-50195: containerd: CRI checkpoint import allows local image tag poisoning
Impact containerd's CRI checkpoint import process contains a vulnerability where it fails to validate the image references specified within a checkpoint image's configuration. An attacker with permissions to create pods can use a crafted checkpoint image to force containerd to pull a malicious image and assign it an arbitrary local tag, thereby poisoning the node's local image cache.
Published Jun 19, 2026 · Updated Jul 21, 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 checkpoint import process contains a vulnerability where it fails to validate the image references specified within a checkpoint image's configuration. An attacker with permissions to create pods can use a crafted checkpoint image to force containerd to pull a malicious image and assign it an arbitrary local tag, thereby poisoning the node's local image cache. Subsequently, if other pods on the same node attempt to use the poisoned tag with an IfNotPresent (or Never) pull policy, they will unknowingly execute the attacker's malicious image instead of the legitimate one. This can lead to a compromise of the affected pods, allowing the attacker to execute arbitrary code under the victim pod's identity.
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.
Workarounds
Users should only allow trusted images to be pulled.
Credits
The containerd project would like to thank Henry Beberman (@hbeberman) of Microsoft, the GKE Security Team using Gemini, Anthropic Research, in collaboration with Claude, and Robert Prast (@robertprast) who independently discovered and responsibly disclosed 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 hbeberman, 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
