Skip to content
VulniPulse
Sign in
Medium 2 vendors · 2 advisories

CVE-2026-47262: containerd image-triggered runtime DoS via unbounded group parsing

CVE-2026-47262 key facts

CISA KEV
Not listed (catalogue checked )
Highest advisory rating
Medium
CVSS base score
6.5 (Red Hat), 5.3 (Docker)
CVSS vector
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 · base score 5.3, scored by GitHub_MAttack vector: network. Attack complexity: low. Attack requirements: none. Privileges required: low. User interaction: none. Confidentiality impact on the vulnerable system: none. Integrity impact on the vulnerable system: none. Availability impact on the vulnerable system: low. Confidentiality impact on subsequent systems: none. Integrity impact on subsequent systems: none. Availability impact on subsequent systems: none.
Weakness
  • CWE-400: Uncontrolled Resource Consumption
EPSS
0.27% chance of exploitation in the next 30 days (18th percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: no. Technical impact: partial. CISA, .
Fixed releases
  • Docker: 1.7.33
  • Red Hat: 1.7.33, 2.0.10, 2.1.9, 2.2.5, 2.3.2, kubernetes1-35-main-1.35.6-1.hum1 and 11 more in the advisory
Vendor advisories
2 from Docker, Red Hat
Assigned by
GitHub_M (CNA)
CVE record published
Listed by VulniPulse
Record changed

Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-47262; each belongs to its advisory, not to every product listed. How records are collected and checked.

Description

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.

Text from the CVE.org record (GitHub_M).

How do I fix CVE-2026-47262?

Upgrade to a fixed release named by the vendor:

  • Docker: 1.7.33
  • Red Hat: 1.7.33, 2.0.10, 2.1.9, 2.2.5, 2.3.2, kubernetes1-35-main-1.35.6-1.hum1
  • No mitigation is needed for Red Hat products. The vulnerable code path in containerd's CRI plugin group-parsing logic is not executed because Red Hat uses CRI-O as the container runtime. Products that bundle containerd as a library dependency for OCI image operations are not affected. (Red Hat)

Vendor advisories for CVE-2026-47262

Docker

1 advisory
  • Advisory severityMedium5.3

    Medium [CVE-2026-47262] Docker Engine: containerd is an open-source container runtime

    CVE-2026-47262Source published Source updated

    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.

    Related products — impact not confirmed
    • Docker Engine
    • containerd
    Source-reported affected versions
    • before 1.7.33
    Source-reported fixed versions
    • 1.7.33
    Mitigation guidance
    No mitigation guidance extracted; consult the source.
    Full advisory and evidenceOpen source bulletin

Red Hat

1 advisory
  • Advisory severityMedium6.5

    Medium [CVE-2026-47262] Denial of Service via maliciously crafted image leading to unbounded group parsing

    CVE-2026-47262Source published Source updated

    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. A remote attacker could exploit this vulnerability by providing a maliciously crafted image. When a container is created from this image, it leads to uncontrolled resource consumption and memory exhaustion, causing the…

    Affected products in this advisory
    • Red Hat Hardened Images
    Source-reported affected versions
    • < 1.7.33
    • < 2.0.10
    • < 2.1.9
    • < 2.2.5

    1 more entries in the full advisory.

    Source-reported fixed versions
    • 1.7.33
    • 2.0.10
    • 2.1.9
    • 2.2.5

    13 more entries in the full advisory.

    Mitigation guidance
    • No mitigation is needed for Red Hat products. The vulnerable code path in containerd's CRI plugin group-parsing logic is not executed because Red Hat uses CRI-O as the container runtime. Products that bundle containerd as a library dependency for OCI image operations are not affected.
    Full advisory and evidenceOpen source bulletin

References

Timeline

  1. CVE record published
  2. CVE record last updated
  3. First vendor advisory listed by VulniPulse

More Docker advisories

All Docker advisories

Get an email when Docker publishes the next one.

See Docker's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Docker

iPhone and Android apps · New on the App Store

Get alerts for new CVEs on your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery
Download on the App StoreGet CVE alerts on AndroidSee app features