CVE-2026-53489

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 89% 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
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0

A fix is available — apply it.

containerd is an open-source container runtime. Versions prior to 2.3.2, 2.2.5 and 2.1.9 contain a bug where the CRI plugin restores container.log from a checkpoint image without validating a symlinked path. This could result in reading an arbitrary file on the host via kubectl logs. This issue has been fixed in versions 2.3.2, 2.2.5 and 2.1.9.

CVSS v3
6.5
EG Score
6.5(medium)
EPSS
11.0%
KEV
Not listed

Published

June 19, 2026

Last Modified

July 2, 2026

Advisory Details (1)

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

Arbitrary host file read via symlink following in CRI checkpoint restore · Advisory · containerd/containerd · GitHub

https://github.com/containerd/containerd/security/advisories/GHSA-rgh6-rfwx-v388

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntucontainerd (2.2.1-0ubuntu1~25.10.2) @ questing2026-07-16ubuntu
ubuntucontainerd-stable (2.2.2-0ubuntu1.1) @ resolute2026-07-16ubuntu
redhatgrype-main-0.115.0-0.1.hum12026-06-29redhat
redhatsyft-main-1.46.0-0.1.hum12026-06-29redhat
redhattrivy-main-0.69.3-1.2.hum12026-05-09redhat

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

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/containerd/containerd/v22.3.2

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

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 9× in last 7d / 55× 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-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:25 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-18 10:04 UTCEPSS rescore
  7. 2026-07-17 04:06 UTCVendor advisory
  8. 2026-07-16 17:03 UTCEPSS rescore
  9. 2026-07-16 05:42 UTCVendor advisory
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 16:57 UTCEPSS rescore
  12. 2026-07-15 07:18 UTCVendor advisory
  13. 2026-07-15 02:00 UTCEPSS rescore
  14. 2026-07-15 02:00 UTCEPSS rescore
  15. 2026-07-14 08:54 UTCVendor advisory
  16. 2026-07-13 22:31 UTCEPSS rescore
  17. 2026-07-13 09:19 UTCVendor advisory
  18. 2026-07-13 06:13 UTCEPSS rescore
  19. 2026-07-13 06:13 UTCEPSS rescore
  20. 2026-07-12 10:52 UTCVendor advisory
  21. 2026-07-12 05:46 UTCEPSS rescore
  22. 2026-07-11 12:28 UTCVendor advisory
  23. 2026-07-11 08:27 UTCEPSS rescore
  24. 2026-07-11 08:27 UTCEPSS rescore
  25. 2026-07-10 14:05 UTCVendor advisory
Show 31 more
  1. 2026-07-09 19:10 UTCEPSS rescore
  2. 2026-07-09 19:10 UTCEPSS rescore
  3. 2026-07-09 15:29 UTCVendor advisory
  4. 2026-07-08 16:59 UTCVendor advisory
  5. 2026-07-08 15:16 UTCEPSS rescore
  6. 2026-07-08 15:16 UTCEPSS rescore
  7. 2026-07-07 18:36 UTCVendor advisory
  8. 2026-07-07 13:46 UTCEPSS rescore
  9. 2026-07-07 13:46 UTCEPSS rescore
  10. 2026-07-06 17:01 UTCVendor advisory
  11. 2026-07-06 16:27 UTCEPSS rescore
  12. 2026-07-06 16:27 UTCEPSS rescore
  13. 2026-07-06 02:23 UTCEPSS rescore
  14. 2026-07-06 02:23 UTCEPSS rescore
  15. 2026-07-05 18:38 UTCVendor advisory
  16. 2026-07-05 02:31 UTCEPSS rescore
  17. 2026-07-05 02:30 UTCEPSS rescore
  18. 2026-07-04 20:15 UTCVendor advisory
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-03 21:50 UTCVendor advisory
  22. 2026-07-02 23:28 UTCEG score recompute 1.70
  23. 2026-07-02 23:28 UTCVendor advisory
  24. 2026-07-02 20:05 UTCNVD updateCVSS v3 → 6.5 · severity → MEDIUM
  25. 2026-07-02 10:18 UTCVendor advisory
  26. 2026-07-01 21:09 UTCEG score recompute 8.20
  27. 2026-07-01 21:09 UTCVendor advisory
  28. 2026-07-01 21:08 UTCNVD updateCVSS v3 → 8.2 · CVSS v4 → 8.2
  29. 2026-06-28 21:40 UTCVendor advisory
  30. 2026-06-25 21:01 UTCVendor advisory
  31. 2026-06-19 19:36 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-53489?
CVE-2026-53489 is a medium vulnerability published on June 19, 2026. containerd is an open-source container runtime. Versions prior to 2.3.2, 2.2.5 and 2.1.9 contain a bug where the CRI plugin restores container.log from a checkpoint image without validating a symlinked path. This could result in reading an arbitrary file on the host via kubectl logs. This issue has…
When was CVE-2026-53489 disclosed?
CVE-2026-53489 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-53489 actively exploited?
CVE-2026-53489 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 11.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53489?
CVE-2026-53489 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-53489?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53489, 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-53489

Explore →

Is Your Infrastructure Affected by CVE-2026-53489?

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