CVE-2026-47262

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]

To report a security issue in containerd:

• Report a new vulnerability
• Email us at [email protected]

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.

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

Kodem intelligence

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.

1. What is CVE-2026-47262? CVE-2026-47262 is a medium-severity uncontrolled resource consumption vulnerability in github.com/containerd/containerd/v2 (go), affecting versions >= 2.0.0, < 2.0.10. It is fixed in 2.0.10, 1.7.33, 2.1.9, 2.2.5, 2.3.2. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
2. Which packages are affected by CVE-2026-47262?
   • github.com/containerd/containerd/v2 (go) (versions >= 2.0.0, < 2.0.10)
   • github.com/containerd/containerd (go) (versions >= 1.7.0, < 1.7.33)
3. Is there a fix for CVE-2026-47262? Yes. CVE-2026-47262 is fixed in 2.0.10, 1.7.33, 2.1.9, 2.2.5, 2.3.2. Upgrade to this version or later.
4. Is CVE-2026-47262 exploitable, and should I be worried? Whether CVE-2026-47262 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
5. What actually determines whether CVE-2026-47262 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
6. How do I fix CVE-2026-47262?
   • Upgrade github.com/containerd/containerd/v2 to 2.0.10 or later
   • Upgrade github.com/containerd/containerd to 1.7.33 or later
   • Upgrade github.com/containerd/containerd/v2 to 2.1.9 or later
   • Upgrade github.com/containerd/containerd/v2 to 2.2.5 or later
   • Upgrade github.com/containerd/containerd/v2 to 2.3.2 or later