CVE-2026-50195

CRITICALNVD 9.99.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 9.9 from GitHub Security Advisory (severity: MODERATE) published 2026-06-19. NVD baseline CVSS 9.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2026-41108 (ENISA EUVD) · GHSA-cvxm-645q-p574 (GitHub Security Advisories)Source: ENISA EUVD

9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • 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
45
EG Risk 45/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
23rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 19, 2026

Last Modified

July 2, 2026

Advisory Details (1)

Auto-updated Oct 30, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

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

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntucontainerd-stable (2.1.6-0ubuntu1~25.10.2) @ questing2026-11-01ubuntu
ubuntucontainerd (2.2.1-0ubuntu1~24.04.3) @ noble2026-11-01ubuntu
redhattrivy-main-0.72.0-0.1.hum12026-07-02redhat
gogithub.com/containerd/containerd/v2 @ 2.1.9 (fixes >= 2.1.0, < 2.1.9)—ghsa
gogithub.com/containerd/containerd/v2 @ 2.2.5 (fixes >= 2.2.0, < 2.2.5)—ghsa
gogithub.com/containerd/containerd/v2 @ 2.3.2 (fixes >= 2.3.0, < 2.3.2)—ghsa

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 24× in last 7d / 78× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 423 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 323 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

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

Frequently asked(5)

What is CVE-2026-50195?
CVE-2026-50195 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-50195 published?
The CVE record for CVE-2026-50195 was published on June 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 2, 2026; the record at its source may have been updated since.
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 (23rd 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