Approved changes feed: RSS · Atom

cpe:2.3:a:anaconda:dask:*:*:*:*:*:python:*:*

part: a version: * update: *

VendorAnaconda (3b46250f-37c4-5689-8080-4097943a18fc)
ProductDask (c654db8b-56cb-5b4b-8d35-fe461b452c1f)
Edition*
Language*
Software edition*
Target softwarepython
Target hardware*
Other*
NotesImported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:deb/debian/dask purl2cpe 2026-06-01 10:12:13.544578
pkg:deb/ubuntu/dask purl2cpe 2026-06-01 10:12:13.544580
pkg:github/dask/dask purl2cpe 2026-06-01 10:12:13.544581
pkg:pypi/dask purl2cpe 2026-06-01 10:12:13.544583
pkg:rpm/fedora/python-dask purl2cpe 2026-06-01 10:12:13.544584
pkg:rpm/opensuse/python-dask purl2cpe 2026-06-01 10:12:13.544585

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-23528 vulnerable 2026-06-08 07:51:15.572929 Dask distributed Vulnerable to Remote Code Execution via Jupyter Proxy and Dashboard
Dask distributed is a distributed task scheduler for Dask. Prior to 2026.1.0, when Jupyter Lab, jupyter-server-proxy, and Dask distributed are all run together, it is possible to craft a URL which will result in code being executed by Jupyter due to a cross-side-scripting (XSS) bug in the Dask dashboard. It is possible for attackers to craft a phishing URL that assumes Jupyter Lab and Dask may be running on localhost and using default ports. If a user clicks on the malicious link it will open an error page in the Dask Dashboard via the Jupyter Lab proxy which will cause code to be executed by the default Jupyter Python kernel. This vulnerability is fixed in 2026.1.0.
Published: 2026-01-16T16:44:28.152Z
Updated: 2026-01-16T17:21:36.324Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2021-42343 vulnerable 2026-06-08 05:35:22.205126 Details available
An issue was discovered in the Dask distributed package before 2021.10.0 for Python. Single machine Dask clusters started with dask.distributed.LocalCluster or dask.distributed.Client (which defaults to using LocalCluster) would mistakenly configure their respective Dask workers to listen on external interfaces (typically with a randomly selected high port) rather than only on localhost. A Dask cluster created using this method (when running on a machine that has an applicable port exposed) could be used by a sophisticated attacker to achieve remote code execution.
Published: 2021-10-26T10:23:26.000Z
Updated: 2024-08-04T03:30:38.314Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.