CVE-2026-50195

CRITICALNVD 9.99.9—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.9 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 77% 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
9.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 9.9Exploit: 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 vulnerability in the CRI checkpoint import process where it fails to validate the image references specified within a checkpoint image's configuration. An attacker with permissions to create pods can use a crafted checkpoint image to force containerd to pull a malicious image and assign it an arbitrary local tag, thereby poisoning the node's local image cache. Subsequently, if other pods on the same node attempt to use the poisoned tag with an IfNotPresent (or Never) pull policy, they will unknowingly execute the attacker's malicious image instead of the legitimate one. This can lead to a compromise of the affected pods, allowing the attacker to execute arbitrary code under the victim pod's identity. This issue has been fixed in versions 2.3.2, 2.2.5 and 2.1.9.

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
49
EG Risk 49/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
Severity99% × 45%
Exploitation0% × 40%
Automatability30% × 15%
EPSS PROB
0.3%
EPSS %ILE
20th
KEV
Not listed

Published

June 19, 2026

Last Modified

July 2, 2026

Advisory Details (1)

Auto-updated Oct 2, 2026
Patch available. Sources: github.
github Patch Available

CRI checkpoint import allows local image tag poisoning · Advisory · containerd/containerd · GitHub

https://github.com/containerd/containerd/security/advisories/GHSA-cvxm-645q-p574

Vendor Advisories for CVE-2026-50195(5)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntucontainerd (2.2.2-0ubuntu1.1) @ resolute2026-09-14ubuntu
ubuntucontainerd-stable (2.2.2-0ubuntu1.1) @ resolute2026-09-14ubuntu
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

(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(2)

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 6× in last 7d / 25× 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 347 total refreshes for this CVE.

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

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

Frequently asked(5)

What is CVE-2026-50195?
CVE-2026-50195 is a critical 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 vulnerability in the CRI checkpoint import process where it fails to validate the image references specified within a checkpoint image's configuration. An attacker with permissions to create pods can…
When was CVE-2026-50195 disclosed?
CVE-2026-50195 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-50195 actively exploited?
CVE-2026-50195 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50195?
CVE-2026-50195 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2026-50195?
A fix for CVE-2026-50195 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-50195 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-50195

Explore →

Is Your Infrastructure Affected by CVE-2026-50195?

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

Book a Demo →Browse All CVEs