Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 16, 2026

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
distributed ==2023.11.0==2026.1.1 age confidence

GitHub Vulnerability Alerts

CVE-2026-23528

Impact

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.

In order for a user to be impacted they must be running Jupyter Lab locally on the default port (with the jupyter-server-proxy) and a Dask distributed cluster on the default port. Then they would need to click the link which would execute the malicious code.

Patches

This has been fixed in the 2026.1.1 release. All users should upgrade to this version.

Mitigations

There are no known workarounds for this bug. The only complete solution is to upgrade to a newer release of Dask. However, there are a few things you could do to reduce your risk.

It is possible to avoid code execution via Jupyter by uninstalling the jupyter-server-proxy and accessing the Dask dashboard directly at it's URL. However, it is still possible for an attacker to craft a URL that executes JavaScript in the user's browser in the Dask dashboard. Which is still a moderate vulnerability. Therefore we recommend all users upgrade to the latest Dask release.

Another potential mitigation is to ensure both Jupyter and the Dask dashboard are running on non-standard ports. While this doesn't resolve the problem it reduces the chance of this being exploited. If an attacker knew which ports you were using they could still craft a malicious URL, but it would require a more targeted attack.


Release Notes

dask/distributed (distributed)

v2026.1.1

Compare Source

Changes

  • No changes

See the Changelog for more information.

v2026.1.0

Compare Source

Changes

See the Changelog for more information.

v2025.12.0

Compare Source

Changes

See the Changelog for more information.

v2025.11.0

Compare Source

Changes

See the Changelog for more information.

v2025.10.0

Compare Source

Changes

See the Changelog for more information.

v2025.9.1

Compare Source

Changes

See the Changelog for more information.

v2025.9.0

Compare Source

Changes

See the Changelog for more information.

v2025.7.0

Compare Source

Changes

See the Changelog for more information.

v2025.5.1

Compare Source

Changes

  • No changes

See the Changelog for more information.

v2025.5.0

Compare Source

Changes

See the Changelog for more information.

v2025.4.1

Compare Source

Changes

  • No changes

See the Changelog for more information.

v2025.4.0

Compare Source

Changes

See the Changelog for more information.

v2025.3.0

Compare Source

Changes

See the Changelog for more information.

v2025.2.0

Compare Source

Changes

See the Changelog for more information.

v2025.1.0

Compare Source

Changes

See the Changelog for more information.

v2024.12.1

Compare Source

Changes

See the Changelog for more information.

v2024.12.0

Compare Source

Changes

See the Changelog for more information.

v2024.11.2

Compare Source

Changes

See the Changelog for more information.

v2024.11.1

Compare Source

Changes

See the Changelog for more information.

v2024.11.0

Compare Source

Changes

See the Changelog for more information.

v2024.10.0

Compare Source

Changes

See the Changelog for more information.

v2024.9.1

Compare Source

Changes

See the Changelog for more information.

v2024.9.0

Compare Source

Changes

See the Changelog for more information.

v2024.8.2

Compare Source

Changes

See the Changelog for more information.

v2024.8.1

Compare Source

Changes

See the Changelog for more information.

v2024.8.0

Compare Source

Changes

See the Changelog for more information.

v2024.7.1

Compare Source

Changes

See the Changelog for more information.

v2024.7.0

Compare Source

Changes


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant