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 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
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.5Exploit: None knownExposed services: Not assessed

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.5MEDIUMmedium confidence
EG Risk
34
EG Risk 34/100

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
Severity65% × 45%
Exploitation0% × 40%
Automatability30% × 15%
EPSS PROB
0.2%
EPSS %ILE
6th
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

Vendor Advisories for CVE-2026-53489(9)

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

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntucontainerd (2.2.2-0ubuntu1.1) @ resolute2026-09-13ubuntu
ubuntucontainerd-stable (2.2.2-0ubuntu1.1) @ resolute2026-09-13ubuntu
redhatodf4/rook-ceph-rhel9-operator:17866295482026-08-19redhat
redhatodf4/rook-ceph-rhel9-operator:17867031432026-08-18redhat
redhatsyft-main-1.46.0-0.1.hum12026-06-29redhat
redhatgrype-main-0.115.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

(3 across 2 ecosystems)
Go(2)
PackageVulnerable rangeFix by version rangeDependents
github.com/containerd/containerd—
  • every version on: no fix on record
—
github.com/containerd/containerd/v2—
  • 2.1.0 up to 2.1.9: fixed in 2.1.9
  • 2.2.0 up to 2.2.5: fixed in 2.2.5
  • 2.3.0 up to 2.3.2: fixed in 2.3.2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
containerd1.7.24~ds1-10 ... 2.1.6+ds1-1 (13 versions)
  • every version up to 2.1.9+ds1-1: fixed in 2.1.9+ds1-1
—

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 7× in last 7d / 24× 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.

Showing the most recent 100 of 172 total refreshes for this CVE.

  1. 2026-10-04 23:22 UTCEPSS rescore
  2. 2026-10-03 14:26 UTCEPSS rescore
  3. 2026-10-02 17:56 UTCEPSS rescore
  4. 2026-10-02 15:10 UTCOSV refresh
  5. 2026-10-01 19:50 UTCEPSS rescore
  6. 2026-09-30 15:03 UTCEPSS rescore
  7. 2026-09-29 15:22 UTCEPSS rescore
  8. 2026-09-28 13:51 UTCEPSS rescore
  9. 2026-09-27 13:48 UTCEPSS rescore
  10. 2026-09-26 15:59 UTCEPSS rescore
  11. 2026-09-24 14:04 UTCEPSS rescore
  12. 2026-09-23 17:54 UTCEPSS rescore
  13. 2026-09-20 20:16 UTCEPSS rescore
  14. 2026-09-18 19:28 UTCEPSS rescore
  15. 2026-09-16 14:08 UTCEPSS rescore
  16. 2026-09-16 05:15 UTCEPSS rescore
  17. 2026-09-13 16:47 UTCEPSS rescore
  18. 2026-09-13 13:08 UTCEG score recompute
  19. 2026-09-13 13:08 UTCVendor advisory
  20. 2026-09-11 14:53 UTCEPSS rescore
  21. 2026-09-10 09:35 UTCEPSS rescore
  22. 2026-09-08 22:01 UTCEPSS rescore
  23. 2026-09-07 16:01 UTCEPSS rescore
  24. 2026-09-06 13:47 UTCEPSS rescore
  25. 2026-09-04 05:06 UTCEPSS rescore
Show 75 more
  1. 2026-08-30 20:47 UTCEG score recompute
  2. 2026-08-30 20:47 UTCVendor advisory
  3. 2026-08-30 19:17 UTCEPSS rescore
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-28 21:41 UTCEPSS rescore
  6. 2026-08-27 14:25 UTCEPSS rescore
  7. 2026-08-26 14:46 UTCEPSS rescore
  8. 2026-08-25 13:49 UTCEPSS rescore
  9. 2026-08-24 22:17 UTCEG score recompute
  10. 2026-08-24 22:17 UTCVendor advisory
  11. 2026-08-23 22:23 UTCEG score recompute
  12. 2026-08-23 22:23 UTCVendor advisory
  13. 2026-08-23 00:19 UTCEPSS rescore
  14. 2026-08-22 23:43 UTCEG score recompute
  15. 2026-08-22 23:43 UTCVendor advisory
  16. 2026-08-21 23:49 UTCEPSS rescore
  17. 2026-08-21 06:24 UTCEG score recompute
  18. 2026-08-21 06:24 UTCVendor advisory
  19. 2026-08-20 22:55 UTCEPSS rescore
  20. 2026-08-20 08:00 UTCEG score recompute
  21. 2026-08-20 08:00 UTCVendor advisory
  22. 2026-08-19 17:04 UTCEPSS rescore
  23. 2026-08-19 07:02 UTCEG score recompute
  24. 2026-08-19 07:02 UTCVendor advisory
  25. 2026-08-18 13:48 UTCEPSS rescore
  26. 2026-08-17 13:47 UTCEPSS rescore
  27. 2026-08-16 22:28 UTCEG score recompute
  28. 2026-08-16 22:28 UTCVendor advisory
  29. 2026-08-16 14:56 UTCEPSS rescore
  30. 2026-08-16 02:14 UTCEPSS rescore
  31. 2026-08-16 00:05 UTCVendor advisory
  32. 2026-08-15 01:41 UTCEG score recompute
  33. 2026-08-15 01:41 UTCVendor advisory
  34. 2026-08-15 01:30 UTCEPSS rescore
  35. 2026-08-14 03:18 UTCEG score recompute
  36. 2026-08-14 03:18 UTCVendor advisory
  37. 2026-08-13 22:00 UTCEPSS rescore
  38. 2026-08-13 04:55 UTCEG score recompute
  39. 2026-08-13 04:55 UTCVendor advisory
  40. 2026-08-12 13:51 UTCEPSS rescore
  41. 2026-08-12 06:32 UTCEG score recompute
  42. 2026-08-12 06:32 UTCVendor advisory
  43. 2026-08-11 08:08 UTCEG score recompute
  44. 2026-08-11 08:08 UTCVendor advisory
  45. 2026-08-11 00:00 UTCEPSS rescore
  46. 2026-08-10 09:45 UTCEG score recompute
  47. 2026-08-10 09:45 UTCVendor advisory
  48. 2026-08-09 13:46 UTCEPSS rescore
  49. 2026-08-09 11:22 UTCEG score recompute
  50. 2026-08-09 11:22 UTCVendor advisory
  51. 2026-08-08 16:37 UTCEPSS rescore
  52. 2026-08-08 12:58 UTCEG score recompute
  53. 2026-08-08 12:58 UTCVendor advisory
  54. 2026-08-07 14:34 UTCVendor advisory
  55. 2026-08-06 16:12 UTCEG score recompute
  56. 2026-08-06 16:12 UTCVendor advisory
  57. 2026-08-06 13:47 UTCEPSS rescore
  58. 2026-08-05 19:17 UTCEPSS rescore
  59. 2026-08-05 17:48 UTCVendor advisory
  60. 2026-08-04 18:30 UTCEG score recompute
  61. 2026-08-04 18:30 UTCVendor advisory
  62. 2026-08-04 15:10 UTCEPSS rescore
  63. 2026-08-04 10:39 UTCEPSS rescore
  64. 2026-08-03 19:13 UTCEG score recompute
  65. 2026-08-03 19:13 UTCVendor advisory
  66. 2026-08-03 10:36 UTCEPSS rescore
  67. 2026-08-02 20:50 UTCEG score recompute
  68. 2026-08-02 20:50 UTCVendor advisory
  69. 2026-08-02 02:27 UTCEPSS rescore
  70. 2026-08-01 22:27 UTCEG score recompute
  71. 2026-08-01 22:27 UTCVendor advisory
  72. 2026-08-01 04:16 UTCEPSS rescore
  73. 2026-08-01 00:04 UTCVendor advisory
  74. 2026-07-31 01:19 UTCEG score recompute
  75. 2026-07-31 01:19 UTCVendor advisory

Related CVEs(same product + same vendor + same CWE)

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 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 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
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?
A fix for CVE-2026-53489 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53489 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs