CVE-2026-53488

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 93% 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 — Patch released this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

containerd is an open-source container runtime. In versions prior to 1.7.33, 2.3.2, 2.2.5, 2.1.9, and 2.0.10 the CRI plugin propagates labels from an image config (LABEL instruction in Dockerfile) to a container without validation. This may result in executing an arbitrary command on the host, via a plugin that consumes container labels for some operations. This issue has been fixed in versions 1.7.33, 2.3.2, 2.2.5, 2.1.9, and 2.0.10.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
44(Track)
EG Risk 44/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
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

June 19, 2026

Last Modified

July 3, 2026

Advisory Details (1)

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

containerd CRI — image-config LABEL flows to host-root command execution from an image pull · Advisory · containerd/containerd · GitHub

https://github.com/containerd/containerd/security/advisories/GHSA-xhf5-7wjv-pqxp

Vendor Advisories for CVE-2026-53488(14)

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

Patch Availability(14)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntucontainerd-stable (2.2.2-0ubuntu1.1) @ resolute2026-07-27ubuntu
ubuntucontainerd (2.2.2-0ubuntu1.1) @ resolute2026-07-27ubuntu
ubuntugolang-github-docker-containerd-dev (1.2.6-0ubuntu1~16.04.6+esm7) @ xenial2026-07-27ubuntu
redhatmulticluster-globalhub/multicluster-globalhub-rhel9-operator:17841517722026-07-23redhat
redhatmulticluster-globalhub/multicluster-globalhub-rhel9-operator:17841275242026-07-21redhat
redhatmulticluster-globalhub/multicluster-globalhub-rhel9-operator:17840605152026-07-16redhat
redhatmulticluster-engine/assisted-service-9-rhel9:17833503552026-07-09redhat
redhatadvanced-cluster-security/rhacs-main-rhel8:17833571402026-07-08redhat
redhatrhacm2/submariner-rhel9-operator:17829331932026-07-08redhat
redhatadvanced-cluster-security/rhacs-scanner-v4-rhel9:17833525892026-07-07redhat
redhatmulticluster-engine/assisted-service-9-rhel9:17833332682026-07-07redhat
redhatadvanced-cluster-security/rhacs-main-rhel8:17833571162026-07-07redhat
redhatmulticluster-engine/assisted-service-8-rhel8:17833320082026-07-07redhat
redhattrivy-main-0.72.0-0.1.hum12026-07-02redhat

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 11× in last 7d / 87× 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-27 03:55 UTCVendor advisory
  2. 2026-07-26 16:49 UTCEG score recompute
  3. 2026-07-26 16:49 UTCVendor advisory
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-25 14:18 UTCEPSS rescore
  6. 2026-07-24 14:18 UTCEPSS rescore
  7. 2026-07-23 14:18 UTCEPSS rescore
  8. 2026-07-23 03:19 UTCEG score recompute
  9. 2026-07-22 14:08 UTCEPSS rescore
  10. 2026-07-21 15:25 UTCEPSS rescore
  11. 2026-07-20 17:08 UTCEPSS rescore
  12. 2026-07-19 14:31 UTCEPSS rescore
  13. 2026-07-19 14:31 UTCEPSS rescore
  14. 2026-07-19 02:29 UTCEPSS rescore
  15. 2026-07-18 10:04 UTCEPSS rescore
  16. 2026-07-16 23:21 UTCVendor advisory
  17. 2026-07-16 17:03 UTCEPSS rescore
  18. 2026-07-16 12:32 UTCVendor advisory
  19. 2026-07-16 01:36 UTCVendor advisory
  20. 2026-07-15 16:57 UTCEPSS rescore
  21. 2026-07-15 16:57 UTCEPSS rescore
  22. 2026-07-15 14:46 UTCVendor advisory
  23. 2026-07-15 03:50 UTCVendor advisory
  24. 2026-07-15 02:00 UTCEPSS rescore
  25. 2026-07-15 02:00 UTCEPSS rescore
Show 64 more
  1. 2026-07-14 17:00 UTCVendor advisory
  2. 2026-07-14 06:09 UTCVendor advisory
  3. 2026-07-13 22:31 UTCEPSS rescore
  4. 2026-07-13 19:15 UTCVendor advisory
  5. 2026-07-13 08:24 UTCVendor advisory
  6. 2026-07-13 06:13 UTCEPSS rescore
  7. 2026-07-13 06:13 UTCEPSS rescore
  8. 2026-07-12 21:34 UTCVendor advisory
  9. 2026-07-12 10:44 UTCVendor advisory
  10. 2026-07-12 05:46 UTCEPSS rescore
  11. 2026-07-11 23:54 UTCVendor advisory
  12. 2026-07-11 13:04 UTCVendor advisory
  13. 2026-07-11 08:27 UTCEPSS rescore
  14. 2026-07-11 08:27 UTCEPSS rescore
  15. 2026-07-11 02:13 UTCVendor advisory
  16. 2026-07-10 15:17 UTCVendor advisory
  17. 2026-07-10 04:16 UTCVendor advisory
  18. 2026-07-09 19:10 UTCEPSS rescore
  19. 2026-07-09 19:10 UTCEPSS rescore
  20. 2026-07-09 17:24 UTCVendor advisory
  21. 2026-07-09 06:29 UTCVendor advisory
  22. 2026-07-08 19:38 UTCVendor advisory
  23. 2026-07-08 15:16 UTCEPSS rescore
  24. 2026-07-08 15:16 UTCEPSS rescore
  25. 2026-07-08 08:48 UTCVendor advisory
  26. 2026-07-07 21:58 UTCVendor advisory
  27. 2026-07-07 13:46 UTCEPSS rescore
  28. 2026-07-07 13:46 UTCEPSS rescore
  29. 2026-07-07 11:08 UTCVendor advisory
  30. 2026-07-06 23:25 UTCVendor advisory
  31. 2026-07-06 16:27 UTCEPSS rescore
  32. 2026-07-06 16:27 UTCEPSS rescore
  33. 2026-07-06 12:34 UTCVendor advisory
  34. 2026-07-06 02:23 UTCEPSS rescore
  35. 2026-07-06 02:23 UTCEPSS rescore
  36. 2026-07-06 01:44 UTCVendor advisory
  37. 2026-07-05 14:54 UTCVendor advisory
  38. 2026-07-05 03:46 UTCVendor advisory
  39. 2026-07-05 02:31 UTCEPSS rescore
  40. 2026-07-05 02:30 UTCEPSS rescore
  41. 2026-07-04 16:53 UTCVendor advisory
  42. 2026-07-04 06:31 UTCEPSS rescore
  43. 2026-07-04 06:31 UTCEPSS rescore
  44. 2026-07-04 05:33 UTCVendor advisory
  45. 2026-07-03 18:43 UTCVendor advisory
  46. 2026-07-03 07:53 UTCVendor advisory
  47. 2026-07-02 21:01 UTCEG score recompute▼ 0.60
  48. 2026-07-02 21:01 UTCVendor advisory
  49. 2026-07-02 20:05 UTCNVD updateCVSS v3 → 8.8 · severity → HIGH
  50. 2026-07-02 16:51 UTCVendor advisory
  51. 2026-07-02 12:39 UTCVendor advisory
  52. 2026-07-02 08:29 UTCVendor advisory
  53. 2026-07-02 04:19 UTCVendor advisory
  54. 2026-07-02 00:09 UTCVendor advisory
  55. 2026-07-01 19:59 UTCVendor advisory
  56. 2026-07-01 15:49 UTCVendor advisory
  57. 2026-07-01 15:07 UTCEPSS rescore
  58. 2026-07-01 11:39 UTCVendor advisory
  59. 2026-07-01 07:30 UTCVendor advisory
  60. 2026-07-01 03:20 UTCEG score recompute▲ 9.40
  61. 2026-07-01 03:20 UTCVendor advisory
  62. 2026-07-01 03:20 UTCNVD updateCVSS v3 → 9.4 · CVSS v4 → 9.4 · severity → CRITICAL
  63. 2026-06-25 18:38 UTCVendor advisory
  64. 2026-06-19 19:36 UTCEG score recompute

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53488?
CVE-2026-53488 is a high vulnerability published on June 19, 2026. containerd is an open-source container runtime. In versions prior to 1.7.33, 2.3.2, 2.2.5, 2.1.9, and 2.0.10 the CRI plugin propagates labels from an image config (LABEL instruction in Dockerfile) to a container without validation. This may result in executing an arbitrary command on the host, via…
When was CVE-2026-53488 disclosed?
CVE-2026-53488 was first published in the National Vulnerability Database on June 19, 2026, with the most recent update on July 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53488 actively exploited?
CVE-2026-53488 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 92.6% of all scored CVEs.
What is the CVSS score of CVE-2026-53488?
CVE-2026-53488 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-53488?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53488, 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-53488

Explore →

Is Your Infrastructure Affected by CVE-2026-53488?

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

Start Free Scan →Browse All CVEs