Cross-site Scripting (XSS) Affecting dask-kubernetes package, versions <2025.7.0-r6


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.02% (6th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Cross-site Scripting (XSS) vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-CHAINGUARDLATEST-DASKKUBERNETES-15050213
  • published22 Jan 2026
  • disclosed16 Jan 2026

Introduced: 16 Jan 2026

CVE-2026-23528  (opens in a new tab)
CWE-79  (opens in a new tab)
CWE-80  (opens in a new tab)
CWE-250  (opens in a new tab)

How to fix?

Upgrade Chainguard dask-kubernetes to version 2025.7.0-r6 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream dask-kubernetes package and not the dask-kubernetes package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

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.