Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The containerd CRI plugin, versions >=2.0.1 and <2.0.5 (Go module github.com/containerd/containerd/v2), does not place containers in user namespaced Kubernetes pods under the Kubernetes cgroup hierarchy, so some Kubernetes resource limits are not enforced. The source does not describe what an attacker must already have, but the effect is that a workload could cause a denial of service on the Kubernetes node. Upgrade to containerd 2.0.5 or later; the source also lists 2.1.0 or later as fixed. Disabling user namespaced pods in Kubernetes is offered as a temporary workaround.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 4.6 | Medium | 4.0 | CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:U | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0029, the 21st percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 21 May 2025, 17:07 UTC Published by the maintainers as a GitHub repository advisory
- 31 Oct 2026, 14:14 UTC First seen by agentprime
- 31 Oct 2026, 14:14 UTC Confirmed by OSV