CVE-2026-47262: containerd image-triggered runtime DoS via unbounded group parsing
Impact A vulnerability in containerd allows a maliciously crafted image to cause a Denial of Service (DoS) condition. When creating a container from this image, memory exhaustion occurs, leading to an Out Of Memory (OOM) kill of the containerd process. This renders the container runtime API unavailable and can disrupt clients such as the Docker Engine or Kubernetes control-plane components.
Published Jun 19, 2026
Affected packages
github.com/containerd/containerd/v2
- Ecosystem
- Go
- Affected
- >= 2.0.0, < 2.0.10
- Fixed in
- 2.0.10
- Check
go list -m github.com/containerd/containerd/v2
github.com/containerd/containerd
- Ecosystem
- Go
- Affected
- >= 1.7.0, < 1.7.33
- Fixed in
- 1.7.33
- Check
go list -m github.com/containerd/containerd
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
A vulnerability in containerd allows a maliciously crafted image to cause a Denial of Service (DoS) condition. When creating a container from this image, memory exhaustion occurs, leading to an Out Of Memory (OOM) kill of the containerd process. This renders the container runtime API unavailable and can disrupt clients such as the Docker Engine or Kubernetes control-plane components.
Patches
This bug has been fixed in the following containerd versions:
- 2.3.2
- 2.2.5
- 2.1.9
- 2.0.10
- 1.7.33
Users should update to these versions to resolve the issue.
Workarounds
Ensure that only trusted images are used and that only trusted users have permissions to import images or schedule pods.
Credits
The containerd project would like to thank Jakub Ciolek (@jake-ciolek) at AlphaSense and Kyle Elliott @ Trail of Bits 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 jake-ciolek, kyle-elliott-tob.
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-50195
containerd: CRI checkpoint import allows local image tag poisoning
medium9.9Jun 19, 2026
