containerd image-triggered runtime DoS via unbounded group parsing
Published 19 Jun 2026 · Updated 10 Sept 2026
Is your project on an affected github.com/containerd/containerd/v2?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=2.0.0 <2.0.10
- Fixed in
- 2.0.10
go get github.com/containerd/containerd/v2@v2.0.10- Affected
- >=1.7.0 <1.7.33
- Fixed in
- 1.7.33
go get github.com/containerd/containerd@v1.7.33- Affected
- >=2.1.0 <2.1.9
- Fixed in
- 2.1.9
go get github.com/containerd/containerd/v2@v2.1.9- Affected
- >=2.2.0 <2.2.5
- Fixed in
- 2.2.5
go get github.com/containerd/containerd/v2@v2.2.5- Affected
- >=2.3.0 <2.3.2
- Fixed in
- 2.3.2
go get github.com/containerd/containerd/v2@v2.3.2Details
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 [security@containerd.io](mailto:security@containerd.io)
To report a security issue in containerd:
- Report a new vulnerability
- Email us at [security@containerd.io](mailto:security@containerd.io)
Is GHSA-jpcc-p29g-p8mq in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/containerd/containerd/v2, and gives you the command that fixes it.
More advisories for github.com/containerd/containerd/v2
- HighCVE-2026-95839containerd image-triggered daemon crash via malformed digest in subject-annotated descriptor · 19 Nov 2026
- LowCVE-2026-95837containerd CRI plugin: Checkpoint restore bypasses destination security context in github.com/containerd/containerd · 19 Oct 2026
- LowCVE-2026-95838containerd: Unpack DoS via repeated opaque whiteouts in github.com/containerd/containerd · 19 Oct 2026
- MediumCVE-2026-95838containerd: Unpack DoS via repeated opaque whiteouts · 15 Oct 2026
- HighCVE-2026-95837containerd CRI plugin: Checkpoint restore bypasses destination security context · 15 Oct 2026
- LowCVE-2026-53493Containerd has image-pull DoS via crafted OCI index graph amplification in github.com/containerd/containerd · 1 Oct 2026
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.