A security vulnerability has been detected in Dask up to 2026.8.0. This affects the function from_npy_stack of the file dask/array/core.py of the component Loader. Such manipulation leads to deserialization. The attack can be launched remotely. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report but has not responded yet.
CVE-2026-95897
MEDIUMPre-NVD 5.55.5—Trending — 5 sources updated this weekElevated
EchelonGraph scoreHIGH confidence
Score 5.5 from GitHub Security Advisory (severity: LOW) published 2026-09-23. a secondary CVSS source baseline 5.5; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: Elevated riskExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.5
- EG Score
- 5.5(high)
- EG Risk
- 25(Track)EG Risk 25/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 computedSeverity55% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 27%
- KEV
- Not listed
Published
September 23, 2026
Last Modified
September 23, 2026
Advisory Details (2)
Auto-updated Sep 23, 2026🔬 Proof of concept available. No patch confirmed yet.
generic
GitHub - dask/dask: Parallel computing with task scheduling · GitHub
https://github.com/dask/dask/generic🟡 PoC Available
dask `from_npy_stack` RCE via Ungated `pickle.load` on the `.npy` Stack `info` Metadata File · Issue #12578 · dask/dask · GitHub
https://github.com/dask/dask/issues/12578Vendor Advisories for CVE-2026-95897(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
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 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.
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-23 15:36 UTCEG score recompute
- 2026-09-23 15:36 UTCGHSA enrichment
- 2026-09-23 15:36 UTCNVD updateCVSS v4 → 2
- 2026-09-23 15:15 UTCEG score recompute
- 2026-09-23 15:14 UTCGHSA enrichment
- 2026-09-23 15:14 UTCMITRE cvelistV5CVSS v4 → 5.1
- 2026-09-23 01:25 UTCEG score recompute
- 2026-09-23 01:25 UTCNVD updateCVSS v4 → 2
- 2026-09-23 00:58 UTCEG score recompute
- 2026-09-23 00:57 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-95897?
CVE-2026-95897 is a medium vulnerability published on September 23, 2026. A security vulnerability has been detected in Dask up to 2026.8.0. This affects the function fromnpystack of the file dask/array/core.py of the component Loader. Such manipulation leads to deserialization. The attack can be launched remotely. The exploit has been disclosed publicly and may be used.…
When was CVE-2026-95897 disclosed?
CVE-2026-95897 was first published in the National Vulnerability Database on September 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-95897 actively exploited?
CVE-2026-95897 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 72.7% of all scored CVEs.
What is the CVSS score of CVE-2026-95897?
CVE-2026-95897 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-95897?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-95897, 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
Explore the affected products and dependency analysis for CVE-2026-95897
Is Your Infrastructure Affected by CVE-2026-95897?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.