CVE-2026-95897Public exploitNetwork attack vectorHinoki check available

Code execution via unguarded metadata unpickling

Published Sep 23, 2026 · Updated Sep 23, 2026

Deserialization in Dask 2026.8.0 and earlier allows attackers to execute code when a crafted array-stack directory is loaded. The from_npy_stack function in dask/array/core.py passes the stack's info metadata file directly to pickle.load without validating its origin or contents. Exploitation requires an application or worker to load an attacker-supplied or attacker-modified stack directory, after which the pickle payload runs with that process's privileges.

CVSS severityUnavailable
Unscored
EPSS probability0.19%
Next 30 days · Oct 19, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Get started

Summary

What happened

Deserialization in Dask 2026.8.0 and earlier allows attackers to execute code when a crafted array-stack directory is loaded. The from_npy_stack function in dask/array/core.py passes the stack's info metadata file directly to pickle.load without validating its origin or contents. Exploitation requires an application or worker to load an attacker-supplied or attacker-modified stack directory, after which the pickle payload runs with that process's privileges.

The record

CVE
CVE-2026-95897
Published
Sep 23, 2026
Updated
Sep 23, 2026
Vendor
Dask
Product
Dask
Classifications
T1204.002
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Sep 23, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 23, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=2026.0
  2. Affected versionversion=2026.1
  3. Affected versionversion=2026.2
  4. Affected versionversion=2026.3
  5. Affected versionversion=2026.4
  6. Affected versionversion=2026.5
  7. Affected versionversion=2026.6
  8. Affected versionversion=2026.7
  9. Affected versionversion=2026.8.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Dask · Daskversion=2026.0; version=2026.1; version=2026.2; version=2026.3; version=2026.4; version=2026.5; version=2026.6; version=2026.7; version=2026.8.0

Published CVSS scores

No CVSS assessment is available in this record.

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Activity data is delayed. The latest report is Sep 28, 2026.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

T1204.002Malicious File

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Get started