CVE-2025-47291: containerd CRI plugin: Incorrect cgroup hierarchy assignment for containers running in usernamespaced Kubernetes pods.
Impact
A bug was found in the containerd's CRI implementation where containerd doesn't put usernamespaced containers under the Kubernetes' cgroup hierarchy, therefore some Kubernetes limits are not honored. This may cause a denial of service of the Kubernetes node.
Patches
This bug has been fixed in containerd 2.0.5+ and 2.1.0+. Users should update to these versions to resolve the issue.
Workarounds
Disable usernamespaced pods in Kubernetes temporarily.
Credits
The containerd project would like to thank Rodrigo Campos Catelin and Piotr Rogowski for responsibly disclosing 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. A bug was found in the containerd's CRI implementation where containerd, starting in version 2.0.1 and prior to version 2.0.5, doesn't put usernamespaced containers under the Kubernetes' cgroup hierarchy, therefore some Kubernetes limits are not honored. This may cause a denial of service of the Kubernetes node. This bug has been fixed in containerd 2.0.5+ and 2.1.0+. Users should update to these versions to resolve the issue. As a workaround, disable usernamespaced pods in Kubernetes temporarily.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-47291?
CVE-2025-47291 is categorized as a medium severity vulnerability.
How do I fix CVE-2025-47291?
To fix CVE-2025-47291, upgrade containerd to version 2.0.5 or later.
What specific versions of containerd are affected by CVE-2025-47291?
CVE-2025-47291 affects containerd versions from 2.0.1 up to, but not including, 2.0.5.
What are the potential consequences of CVE-2025-47291?
The vulnerability may cause usernamespaced containers to not respect Kubernetes cgroup hierarchy, leading to resource limits being ignored.
Is it safe to use containerd versions prior to 2.0.5?
Using containerd versions prior to 2.0.5 is not safe due to the presence of CVE-2025-47291, which can lead to resource management issues.