containerd is an open-source container runtime. From 2.2.0 until 2.2.10, 2.3.7, and 2.4.2, image manifest processing through the transfer service can encounter a child descriptor containing the io.containerd.manifest.subject annotation and a malformed digest. Pulling or importing such an image, including through a default CRI PullImage request, can trigger an unrecovered panic and crash the containerd daemon. In Kubernetes, kubelet retries can repeatedly trigger the crash and disrupt container operations on the worker node. This issue is fixed in versions 2.2.10, 2.3.7, and 2.4.2.
CVE-2026-95839
“—” beside the score: it is equal to the CVSS score beside it.
This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (34th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-126626 (ENISA EUVD) · GHSA-vwhp-8p66-mq4f (GitHub Security Advisories)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS
- 7.1
- EG Score
- 7.1HIGHmedium confidence
- EG Risk
- 32EG Risk 32/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)Severity71% × 45%Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.4% × 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.4%
- EPSS %ILE
- 34th
- 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 (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
- EG Likelihood
- 0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-19). 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
November 16, 2026
Last Modified
November 18, 2026
Advisory Details (8)
Auto-updated Nov 16, 2026containerd: daemon crash when processing an image manifest with a malformed digest · Advisory · containerd/containerd · GitHub
https://github.com/containerd/containerd/security/advisories/GHSA-vwhp-8p66-mq4fcontainerd 2.4.2
Patch available: containerd/containerd v2.4.2
https://github.com/containerd/containerd/releases/tag/v2.4.2containerd 2.3.7
Patch available: containerd/containerd v2.3.7
https://github.com/containerd/containerd/releases/tag/v2.3.7containerd 2.2.10
Patch available: containerd/containerd v2.2.10
https://github.com/containerd/containerd/releases/tag/v2.2.10commit a2eb01f667b3 (containerd/containerd)
Fix landed in containerd/containerd commit a2eb01f667b3 — awaiting tagged release
https://github.com/containerd/containerd/commit/a2eb01f667b320b00ec218216f26f7b79197d4cdcommit 2455fec2f7bf (containerd/containerd)
Fix landed in containerd/containerd commit 2455fec2f7bf — awaiting tagged release
https://github.com/containerd/containerd/commit/2455fec2f7bfa63adb1f993c63ba0cea9cdedb8ccommit 2181d7baa2a3 (containerd/containerd)
Fix landed in containerd/containerd commit 2181d7baa2a3 — awaiting tagged release
https://github.com/containerd/containerd/commit/2181d7baa2a303ea2082e5c0f1a7697787b61ef2commit 20a3b3139065 (containerd/containerd)
Fix landed in containerd/containerd commit 20a3b3139065 — awaiting tagged release
https://github.com/containerd/containerd/commit/20a3b31390653d7a83fdaeb0c318b01a263c9d9aVendor Advisories for CVE-2026-95839(4)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- GHSA-vwhp-8p66-mq4fGitHub Security AdvisoriesHigh
containerd image-triggered daemon crash via malformed digest in subject-annotated descriptor
- CVE-2026-95839Microsoft Security Response Center (MSRC)
Microsoft security update for CVE-2026-95839
- RHSA-2026:100124Red Hat Product SecurityMedium
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
- RHSA-2026:96773Red Hat Product SecurityMedium
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
Patch Availability(3)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| go | github.com/containerd/containerd/v2 @ 2.2.10 (fixes >= 2.2.0, < 2.2.10) | — | ghsa |
| go | github.com/containerd/containerd/v2 @ 2.4.2 (fixes >= 2.4.0, < 2.4.2) | — | ghsa |
| go | github.com/containerd/containerd/v2 @ 2.3.7 (fixes >= 2.3.0, < 2.3.7) | — | ghsa |
These rows come from GitHub (GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 11× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-21 16:42 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-11-20 16:39 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-11-20 01:44 UTCEchelonGraph re-scored
- 2026-11-20 01:44 UTCVendor advisory
- 2026-11-20 01:44 UTCGHSA enrichmentGHSA-vwhp-8p66-mq4f · GitHub severity HIGH
- 2026-11-19 16:36 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-11-18 16:36 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-11-18 16:28 UTCEchelonGraph re-scored
- 2026-11-18 16:28 UTCVendor advisory
- 2026-11-18 15:33 UTCEchelonGraph re-scored
- 2026-11-18 15:33 UTCVendor advisory
- 2026-11-17 16:36 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-11-16 21:02 UTCENISA EUVD ID recordedEUVD-2026-126626 · Source: ENISA EUVD
- 2026-11-16 20:23 UTCEchelonGraph re-scoredFirst assessed: 7.1 HIGH
- 2026-11-16 20:19 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-95839?
When was the CVE record for CVE-2026-95839 published?
Is CVE-2026-95839 actively exploited?
What is the CVSS score of CVE-2026-95839?
How do I remediate CVE-2026-95839?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-95839
Is Your Infrastructure Affected by CVE-2026-95839?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.