CVE-2026-47262

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 82% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
18%
KEV
Not listed

Published

June 19, 2026

Last Modified

July 2, 2026

Advisory Details (1)

Auto-updated Jul 3, 2026
Patch available. Sources: github.
github Patch Available

containerd image-triggered runtime DoS via unbounded group parsing · Advisory · containerd/containerd · GitHub

https://github.com/containerd/containerd/security/advisories/GHSA-jpcc-p29g-p8mq

Vendor Advisories for CVE-2026-47262(9)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntucontainerd-stable (2.2.2-0ubuntu1.1) @ resolute2026-07-26ubuntu
ubuntucontainerd (1.7.24-0ubuntu1~20.04.2+esm2) @ focal2026-07-26ubuntu
ubuntugolang-github-containerd-containerd-dev (1.6.12-0ubuntu1~22.04.11) @ jammy2026-07-26ubuntu
redhattrivy-main-0.72.0-0.1.hum12026-07-02redhat
redhatsyft-main-1.46.0-0.1.hum12026-06-29redhat
redhatgrype-main-0.115.0-0.1.hum12026-06-29redhat
redhatopentelemetry-collector-contrib-main-0.155.0-0.1.hum12026-06-25redhat
redhatkubernetes1-36-main-1.36.2-2.hum12026-06-18redhat
redhatkubernetes1-35-main-1.35.6-1.hum12026-06-12redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 1 ecosystem)
Go(2)
PackageVulnerable rangeFixed inDependents
github.com/containerd/containerd—1.7.33—
github.com/containerd/containerd/v2—2.3.2—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(3)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 47× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-26 16:50 UTCEG score recompute
  2. 2026-07-26 16:50 UTCVendor advisory
  3. 2026-07-26 14:54 UTCEPSS rescore
  4. 2026-07-25 14:18 UTCEPSS rescore
  5. 2026-07-24 14:18 UTCEPSS rescore
  6. 2026-07-23 14:18 UTCEPSS rescore
  7. 2026-07-23 03:17 UTCEG score recompute
  8. 2026-07-22 14:08 UTCEPSS rescore
  9. 2026-07-21 15:24 UTCEPSS rescore
  10. 2026-07-20 17:08 UTCEPSS rescore
  11. 2026-07-19 14:31 UTCEPSS rescore
  12. 2026-07-19 02:29 UTCEPSS rescore
  13. 2026-07-18 10:04 UTCEPSS rescore
  14. 2026-07-16 17:03 UTCEPSS rescore
  15. 2026-07-16 14:31 UTCVendor advisory
  16. 2026-07-15 16:57 UTCEPSS rescore
  17. 2026-07-15 14:27 UTCVendor advisory
  18. 2026-07-15 02:00 UTCEPSS rescore
  19. 2026-07-14 14:51 UTCVendor advisory
  20. 2026-07-13 22:30 UTCEPSS rescore
  21. 2026-07-13 15:24 UTCVendor advisory
  22. 2026-07-13 06:13 UTCEPSS rescore
  23. 2026-07-12 15:54 UTCVendor advisory
  24. 2026-07-12 05:46 UTCEPSS rescore
  25. 2026-07-11 16:30 UTCVendor advisory
Show 24 more
  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-10 17:07 UTCVendor advisory
  3. 2026-07-09 19:10 UTCEPSS rescore
  4. 2026-07-09 17:36 UTCVendor advisory
  5. 2026-07-08 18:03 UTCVendor advisory
  6. 2026-07-08 15:16 UTCEPSS rescore
  7. 2026-07-07 18:37 UTCVendor advisory
  8. 2026-07-06 18:57 UTCVendor advisory
  9. 2026-07-06 16:27 UTCEPSS rescore
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-05 18:45 UTCVendor advisory
  12. 2026-07-05 02:30 UTCEPSS rescore
  13. 2026-07-04 19:21 UTCVendor advisory
  14. 2026-07-04 06:31 UTCEPSS rescore
  15. 2026-07-03 19:57 UTCVendor advisory
  16. 2026-07-02 20:34 UTCEG score recompute▲ 0.20
  17. 2026-07-02 20:34 UTCVendor advisory
  18. 2026-07-02 20:05 UTCNVD updateCVSS v3 → 5.5
  19. 2026-07-01 21:09 UTCEG score recompute▲ 5.30
  20. 2026-07-01 21:09 UTCVendor advisory
  21. 2026-07-01 21:08 UTCNVD updateCVSS v3 → 5.3 · CVSS v4 → 5.3
  22. 2026-06-29 17:33 UTCVendor advisory
  23. 2026-06-26 11:15 UTCVendor advisory
  24. 2026-06-19 19:36 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-47262?
CVE-2026-47262 is a medium vulnerability published on June 19, 2026. 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…
When was CVE-2026-47262 disclosed?
CVE-2026-47262 was first published in the National Vulnerability Database on June 19, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47262 actively exploited?
CVE-2026-47262 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 81.8% of all scored CVEs.
What is the CVSS score of CVE-2026-47262?
CVE-2026-47262 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-47262?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47262, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47262

Explore →

Is Your Infrastructure Affected by CVE-2026-47262?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs