Vulnerability Database · PyPI · distributed · Version
distributed 2024.9.0
2024.9.0 is affected by 2 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 2026.8.0.
Critical 0 High 0 Medium 2 Low 0 Unrated 0
-
Released 13 Sep 2024
Licence BSD-3-Clause
Also known from other sources 2
Newer releases 269
Database updated 23/Oct/2026
Release and licence data published by PyPI. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
distributed 2024.9.0 vulnerabilities
2 vulnerabilities cover distributed 2024.9.0. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2026-23528: Dask Distributed XSS Vulnerability in Jupyter Lab Integration | 6.1 medium | 2026.1.0 | 16 Jan 2026 |
| CVE-2026-23528: Dask Distributed Remote Code Execution Vulnerability via Jupyter Proxy and Dashboard | 5.3 medium | 2026.1.1 | 16 Jan 2026 |
Looking for another version, or everything Vulert holds for distributed?
Questions
About distributed 2024.9.0
Is distributed 2024.9.0 vulnerable?
Yes. 2 vulnerabilities in the Vulert database cover distributed 2024.9.0: 0 critical, 0 high, 2 medium and 0 low. The upgrade Vulert recommends is 2026.8.0, and each entry above names the fixed version to move to.
Which version of distributed should I use instead of 2024.9.0?
2026.8.0 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 2024.9.0 the latest release of distributed?
No. 2024.9.0 was published 13 Sep 2024, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor distributed for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the distributed version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.