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.
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
To report a security issue in containerd: Report a new vulnerability Email us at security@containerd.io
Other sources
containerd is an open-source container runtime. Versions prior to 1.7.33, 2.0.10, 2.1.9, 2.2.5 and 2.3.2, contain a vulnerability that 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. This issue has been fixed in versions 1.7.33, 2.0.10, 2.1.9, 2.2.5 and 2.3.2.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
go/github.com/containerd/containerd/v2to a version that resolves this vulnerability.Fixed in 2.3.2 - Upgrade
Upgrade
go/github.com/containerd/containerd/v2to a version that resolves this vulnerability.Fixed in 2.2.5 - Upgrade
Upgrade
go/github.com/containerd/containerd/v2to a version that resolves this vulnerability.Fixed in 2.1.9 - Upgrade
Upgrade
go/github.com/containerd/containerdto a version that resolves this vulnerability.Fixed in 1.7.33 - Upgrade
Upgrade
go/github.com/containerd/containerd/v2to a version that resolves this vulnerability.Fixed in 2.0.10 - Upgrade
Upgrade
debian/containerdto a version that resolves this vulnerability.Fixed in 2.1.9+ds1-1 - Upgrade
Upgrade
containerdto a version that resolves this vulnerability.Fixed in 1.7.33 - Upgrade
Upgrade
containerdto a version that resolves this vulnerability.Fixed in 2.0.10 - Upgrade
Upgrade
containerdto a version that resolves this vulnerability.Fixed in 2.1.9 - Upgrade
Upgrade
containerdto a version that resolves this vulnerability.Fixed in 2.2.5 - Upgrade
Upgrade
containerdto a version that resolves this vulnerability.Fixed in 2.3.2 - Compensating control
Ensure that only trusted images are used, and only trusted users have permissions to import images or schedule pods (mitigates image-triggered runtime DoS).
Event History
Frequently Asked Questions
What is the severity of CVE-2026-47262?
CVE-2026-47262 has a medium severity rating of 5.3.
How does CVE-2026-47262 affect containerd?
CVE-2026-47262 allows a maliciously crafted image to cause a Denial of Service condition by exhausting memory when creating a container.
How do I fix CVE-2026-47262?
To fix CVE-2026-47262, update to the latest version of containerd that includes the vulnerability patch.
What can trigger the vulnerability in CVE-2026-47262?
The vulnerability in CVE-2026-47262 can be triggered by creating a container from a maliciously crafted image.
What are the consequences of CVE-2026-47262?
The consequences of CVE-2026-47262 include memory exhaustion, leading to an Out Of Memory kill of the containerd process.