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 74% 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
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%CVSS: 9.9Exploit: None knownExposed: 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 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.9(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity99% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

June 19, 2026

Last Modified

July 2, 2026

Advisory Details (1)

Auto-updated Jul 24, 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(4)

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 / EcosystemFixed in / PatchReleasedSource
ubuntucontainerd (2.2.2-0ubuntu1.1) @ resolute2026-07-26ubuntu
ubuntucontainerd-stable (2.2.2-0ubuntu1.1) @ resolute2026-07-26ubuntu
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———
github.com/containerd/containerd/v2—2.3.2—

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 14× in last 7d / 122× 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 124 total refreshes for this CVE.

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

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 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-50195 actively exploited?
CVE-2026-50195 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 74.3% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50195, 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-50195

Explore →

Is Your Infrastructure Affected by CVE-2026-50195?

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

Start Free Scan →Browse All CVEs