containerd · containerd · published 2026-07-01
CVE-2026-47262containerd image-triggered runtime DoS via unbounded group parsing
Routine No exploitation evidence; EPSS 0.3%.
CVE-2026-47262 is not known to be exploited in the wild. EPSS estimates a 0.3% chance of exploitation in the next 30 days, higher than 18% of all CVEs. This containerd vulnerability: CVSS 5.3 (v4.0). Fixed upstream in containerd 2.3.2, 2.2.5, 2.1.9, 2.0.10 (+1 more). Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in containerd 2.3.2, 2.2.5, 2.1.9, 2.0.10, 1.7.33.
Patch events
Container runtimecontainerd
containerd security releases: 2.3.2, 2.2.5, 2.1.9, 2.0.10, 1.7.33
Upgrade to
2.3.22.2.52.1.92.0.101.7.33Why: Vendor security release for server software (most severe: CVE-2026-53488).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.3% (19th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 5.3 (v4.0)CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- containerd containerd
>= 1.7.0, < 1.7.33(affected)>= 2.0.0, < 2.0.10(affected)>= 2.1.0, < 2.1.9(affected)>= 2.2.0, < 2.2.5(affected)>= 2.3.0, < 2.3.2(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.