containerd is an open-source container runtime. From 2.1.0 until 2.2.7 and 2.3.4, containerd's CRI CreateContainer checkpoint restore is vulnerable because CRIU restores process security state from checkpoint data instead of enforcing the destination ContainerConfig. An attacker who can create a container from a crafted checkpoint can supply restored credentials, capabilities, no_new_privs, and seccomp state. The restored process can run as root with full capabilities and no enforced seccomp filters while CRI status reports the requested configuration. Systems that do not use CRI checkpoint restore are not affected. This issue is fixed in versions 2.2.7 and 2.3.4.
CVE-2026-95837
HIGHPre-NVD 7.87.8Trending — 3 sources updated this week
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-10-15. A secondary CVSS source baseline 7.8; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Also known asEUVD-2026-97820 (ENISA EUVD) · GHSA-p7v4-vr35-mj6f (GitHub Security Advisories)Source: ENISA EUVD
7.8EG
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.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 7.8
- EG Score
- 7.8HIGHhigh confidence
- EG Risk
- 35EG Risk 35/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)Severity78% × 45%Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.1% × 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 low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.1%
- EPSS %ILE
- 1st
- 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.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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 low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 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 low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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
October 12, 2026
Last Modified
October 16, 2026
Advisory Details (3)
Auto-updated Oct 12, 2026Patch available. Sources: github, github_pr, github_commit.
GitHub commit
commit 928c03c6898c (containerd/containerd)
Fix landed in containerd/containerd commit 928c03c6898c — awaiting tagged release
https://github.com/containerd/containerd/commit/928c03c6898cad95f795300281fdff0dbc55a32fGitHub pull request
[release/2.3] cri: disable restore in CreateContainer by default
Fix merged in containerd/containerd PR #13913 on 2026-08-10 — awaiting tagged release
https://github.com/containerd/containerd/pull/13913GitHub advisoryMentions a patch (unverified)
containerd CRI plugin: Checkpoint restore bypasses destination security context · Advisory · containerd/containerd · GitHub
https://github.com/containerd/containerd/security/advisories/GHSA-p7v4-vr35-mj6fVendor Advisories for CVE-2026-95837(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(2)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| go | github.com/containerd/containerd/v2 @ 2.2.7 (fixes >= 2.1.0, < 2.2.7) | — | ghsa |
| go | github.com/containerd/containerd/v2 @ 2.3.4 (fixes >= 2.3.0, < 2.3.4) | — | 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
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| github.com/containerd/containerd/v2 | — |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 29× 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.
- 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-11-01 07:37 UTCGHSA enrichmentGHSA-p7v4-vr35-mj6f · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-11-01 07:37 UTCEG score recompute
- 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-31 15:57 UTCEG score recompute
- 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-25 13:48 UTCEG score recompute
- 2026-10-24 04:06 UTCEG score recompute
- 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-18 02:57 UTCEG score recompute
- 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-16 16:09 UTCEG score recompute
- 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-13 18:26 UTCEG score recompute
- 2026-10-13 17:37 UTCEG score recompute
Show 4 moreShow fewer
- 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-12 20:26 UTCEG score recompute
- 2026-10-12 19:47 UTCEG score recomputeFirst assessed: 7.8 HIGH
- 2026-10-12 19:45 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
10 shownGo:github.com/containerd/containerd/v2
Frequently asked(5)
What is CVE-2026-95837?
CVE-2026-95837 is a high-severity vulnerability; its CVE record was published on October 12, 2026. containerd is an open-source container runtime. From 2.1.0 until 2.2.7 and 2.3.4, containerd's CRI CreateContainer checkpoint restore is vulnerable because CRIU restores process security state from checkpoint data instead of enforcing the destination ContainerConfig. An attacker who can create a…
When was the CVE record for CVE-2026-95837 published?
The CVE record for CVE-2026-95837 was published on October 12, 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 October 16, 2026; the record at its source may have been updated since.
Is CVE-2026-95837 actively exploited?
CVE-2026-95837 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-95837?
CVE-2026-95837 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-95837?
A fix for CVE-2026-95837 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-95837 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-95837
Is Your Infrastructure Affected by CVE-2026-95837?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.