VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

distributed: vulnerability history, versions and safety

distributed is a package in the PyPI ecosystem. Vulert records 5 vulnerabilities for it across 112 releases, from Oct 2021 to Jan 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded C1 M1 U3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 16 Jan 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all distributed vulnerabilities

Vulert verdict on distributed 2026.8.0 i

Updated on 23 Oct 2026

Good news: 2026.8.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 5.

Package health score 76/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

What to do: Stay on 2026.8.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 2026.8.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2026.8.0 — unaffected i
  • Vulnerabilities on record 5 over 4 years · 2 in the last year i
  • Latest disclosure 16 Jan 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 1,220 packages i
  • Stars 1,696 i
  • OpenSSF scorecard 4/10 i
  • Last release 1 month ago i
  • Licence BSD-3-Clause i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. 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 Versions

Which versions are affected

Every version Vulert tracks for distributed, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2026.8.0 24 Aug 2026 none BSD-3-Clause — Details →
2026.1.3 14 Jul 2026 none BSD-3-Clause — Details →
2025.9.3 14 Jul 2026 M1 U1 BSD-3-Clause Yes Details →
2026.7.1 14 Jul 2026 none BSD-3-Clause — Details →
2026.7.0 06 Jul 2026 none BSD-3-Clause — Details →
2026.6.0 11 Jun 2026 none BSD-3-Clause — Details →
2026.3.0 18 Mar 2026 none BSD-3-Clause — Details →
2026.1.2 30 Jan 2026 none BSD-3-Clause — Details →
2025.3.1 29 Jan 2026 U1 BSD-3-Clause Yes Details →
2025.9.2 26 Jan 2026 U1 BSD-3-Clause Yes Details →
2026.1.1 16 Jan 2026 none BSD-3-Clause — Details →
2026.1.0 16 Jan 2026 M1 BSD-3-Clause Yes Details →
2025.12.0 12 Dec 2025 M1 U1 BSD-3-Clause Yes Details →
2025.11.0 06 Nov 2025 M1 U1 BSD-3-Clause Yes Details →
2025.10.0 14 Oct 2025 M1 U1 BSD-3-Clause Yes Details →
2025.9.1 16 Sep 2025 M1 U1 BSD-3-Clause Yes Details →
2025.9.0 10 Sep 2025 M1 U1 BSD-3-Clause Yes Details →
2025.7.0 14 Jul 2025 M1 U1 BSD-3-Clause Yes Details →
2025.5.1 20 May 2025 M1 U1 BSD-3-Clause Yes Details →
2025.5.0 13 May 2025 M1 U1 BSD-3-Clause Yes Details →
2025.4.1 25 Apr 2025 M1 U1 BSD-3-Clause Yes Details →
2025.4.0 22 Apr 2025 M1 U1 BSD-3-Clause Yes Details →
2025.3.0 21 Mar 2025 M1 U1 BSD-3-Clause Yes Details →
2025.2.0 13 Feb 2025 M1 U1 BSD-3-Clause Yes Details →
2025.1.0 17 Jan 2025 M1 U1 BSD-3-Clause Yes Details →
2024.12.1 17 Dec 2024 M1 U1 BSD-3-Clause Yes Details →
2024.12.0 03 Dec 2024 M1 U1 BSD-3-Clause Yes Details →
2024.11.2 13 Nov 2024 M1 U1 BSD-3-Clause Yes Details →
2024.11.1 11 Nov 2024 M1 U1 BSD-3-Clause Yes Details →
2024.11.0 08 Nov 2024 M1 U1 BSD-3-Clause Yes Details →
2024.10.0 17 Oct 2024 M1 U1 BSD-3-Clause Yes Details →
2024.9.1 28 Sep 2024 M1 U1 BSD-3-Clause Yes Details →
2024.9.0 13 Sep 2024 M1 U1 BSD-3-Clause Yes Details →
2024.8.2 30 Aug 2024 M1 U1 BSD-3-Clause Yes Details →
2024.8.1 16 Aug 2024 M1 U1 BSD-3-Clause Yes Details →
2024.8.0 06 Aug 2024 M1 U1 BSD-3-Clause Yes Details →
2024.7.1 20 Jul 2024 M1 U1 BSD-3-Clause Yes Details →
2024.7.0 05 Jul 2024 M1 U1 BSD-3-Clause Yes Details →
2024.6.2 20 Jun 2024 M1 U1 BSD-3-Clause Yes Details →
2024.6.1 19 Jun 2024 M1 U1 BSD-3-Clause Yes Details →
2024.6.0 14 Jun 2024 M1 U1 BSD-3-Clause Yes Details →
2024.5.2 31 May 2024 M1 U1 BSD-3-Clause Yes Details →
2024.5.1 17 May 2024 M1 U1 BSD-3-Clause Yes Details →
2024.5.0 03 May 2024 M1 U1 BSD-3-Clause Yes Details →
2024.4.2 19 Apr 2024 M1 U1 BSD-3-Clause Yes Details →
2024.4.1 04 Apr 2024 M1 U1 BSD-3-Clause Yes Details →
2024.4.0 01 Apr 2024 M1 U1 BSD-3-Clause Yes Details →
2024.3.1 15 Mar 2024 M1 U1 BSD-3-Clause Yes Details →
2024.3.0 12 Mar 2024 M1 U1 BSD-3-Clause Yes Details →
2024.2.1 23 Feb 2024 M1 U1 BSD-3-Clause Yes Details →
2024.2.0 09 Feb 2024 M1 U1 BSD-3-Clause Yes Details →
2024.1.1 26 Jan 2024 M1 U1 BSD-3-Clause Yes Details →
2024.1.0 12 Jan 2024 M1 U1 BSD-3-Clause Yes Details →
2023.12.1 15 Dec 2023 M1 U1 BSD-3-Clause Yes Details →
2023.12.0 01 Dec 2023 M1 U1 BSD-3-Clause Yes Details →
2023.11.0 10 Nov 2023 M1 U1 BSD-3-Clause Yes Details →
2023.10.1 27 Oct 2023 M1 U1 BSD-3-Clause Yes Details →
2023.10.0 14 Oct 2023 M1 U1 BSD-3-Clause Yes Details →
2023.9.3 29 Sep 2023 M1 U1 BSD-3-Clause Yes Details →
2023.9.2 15 Sep 2023 M1 U1 BSD-3-Clause Yes Details →
2023.9.1 06 Sep 2023 M1 U1 BSD-3-Clause Yes Details →
2023.9.0 01 Sep 2023 M1 U1 BSD-3-Clause Yes Details →
2023.8.1 18 Aug 2023 M1 U1 BSD-3-Clause Yes Details →
2023.8.0 04 Aug 2023 M1 U1 BSD-3-Clause Yes Details →
2023.7.1 20 Jul 2023 M1 U1 non-standard Yes Details →
2023.7.0 07 Jul 2023 M1 U1 non-standard Yes Details →
2023.6.1 26 Jun 2023 M1 U1 non-standard Yes Details →
2023.6.0 09 Jun 2023 M1 U1 non-standard Yes Details →
2023.5.1 26 May 2023 M1 U1 non-standard Yes Details →
2023.5.0 12 May 2023 M1 U1 non-standard Yes Details →
2023.4.1 28 Apr 2023 M1 U1 non-standard Yes Details →
2023.4.0 14 Apr 2023 M1 U1 non-standard Yes Details →
2023.3.2.1 05 Apr 2023 M1 U1 non-standard Yes Details →
2023.3.2 24 Mar 2023 M1 U1 non-standard Yes Details →
2023.3.1 10 Mar 2023 M1 U1 non-standard Yes Details →
2023.3.0 01 Mar 2023 M1 U1 non-standard Yes Details →
2023.2.1 24 Feb 2023 M1 U1 non-standard Yes Details →
2023.2.0 10 Feb 2023 M1 U1 non-standard Yes Details →
2023.1.1 27 Jan 2023 M1 U1 non-standard Yes Details →
2023.1.0 13 Jan 2023 M1 U1 non-standard Yes Details →
2022.12.1 16 Dec 2022 M1 U1 non-standard Yes Details →
2022.12.0 02 Dec 2022 M1 U1 non-standard Yes Details →
2022.11.1 18 Nov 2022 M1 U1 non-standard Yes Details →
2022.11.0 15 Nov 2022 M1 U1 non-standard Yes Details →
2022.10.2 31 Oct 2022 M1 U1 non-standard Yes Details →
2022.10.1 28 Oct 2022 M1 U1 non-standard Yes Details →
2022.10.0 14 Oct 2022 M1 U1 non-standard Yes Details →
2022.9.2 30 Sep 2022 M1 U1 non-standard Yes Details →
2022.9.1 16 Sep 2022 M1 U1 non-standard Yes Details →
2022.9.0 02 Sep 2022 M1 U1 non-standard Yes Details →
2022.8.1 19 Aug 2022 M1 U1 non-standard Yes Details →
2022.8.0 05 Aug 2022 M1 U1 non-standard Yes Details →
2022.7.1 22 Jul 2022 M1 U1 non-standard Yes Details →
2022.7.0 08 Jul 2022 M1 U1 non-standard Yes Details →
2022.6.1 24 Jun 2022 M1 U1 non-standard Yes Details →
2022.6.0 10 Jun 2022 M1 U1 non-standard Yes Details →
2022.5.2 26 May 2022 M1 U1 non-standard Yes Details →
2022.5.1 24 May 2022 M1 U1 non-standard Yes Details →
2022.5.0 02 May 2022 M1 U1 non-standard Yes Details →
2022.4.2 29 Apr 2022 M1 U1 non-standard Yes Details →
2022.4.1 15 Apr 2022 M1 U1 — Yes Details →
2022.4.0 01 Apr 2022 M1 U1 — Yes Details →
2022.3.0 18 Mar 2022 M1 U1 — Yes Details →
2022.2.1 25 Feb 2022 M1 U1 — Yes Details →
2022.2.0 11 Feb 2022 M1 U1 — Yes Details →
2022.1.1 28 Jan 2022 M1 U1 — Yes Details →
2022.1.0 14 Jan 2022 M1 U1 — Yes Details →
2021.12.0 10 Dec 2021 M1 U1 — Yes Details →
2021.11.2 19 Nov 2021 M1 U1 — Yes Details →
2021.11.1 08 Nov 2021 M1 U1 — Yes Details →
2021.11.0 05 Nov 2021 M1 U1 — Yes Details →
2021.10.0 22 Oct 2021 M1 U1 — Yes Details →
2021.9.1 21 Sep 2021 C1 M1 U3 — Yes Details →
2021.9.0 03 Sep 2021 C1 M1 U3 — Yes Details →
2021.8.1 20 Aug 2021 C1 M1 U3 — Yes Details →
2021.8.0 13 Aug 2021 C1 M1 U3 — Yes Details →
2021.7.2 30 Jul 2021 C1 M1 U3 — Yes Details →
2021.7.1 23 Jul 2021 C1 M1 U3 — Yes Details →
2021.7.0 09 Jul 2021 C1 M1 U3 — Yes Details →
2021.6.2 22 Jun 2021 C1 M1 U3 — Yes Details →

The newest 120 of 285 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 2
  • 2022 1
  • 2026 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 5 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for distributed

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Vulnerability in distributed package: Workers for local Dask clusters mistakenly listened on public interfaces 9.8 critical 2021.10.0 15 Jul 2022
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
CVE-2021-42343: Dask distributed Package Remote Code Execution N/A unrated 2021.10.0 26 Oct 2021
CVE-2021-42343: Dask distributed Package Remote Code Execution N/A unrated 2021.10.0 26 Oct 2021

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About distributed

Is distributed safe to use?

Vulert records 5 vulnerabilities for distributed in PyPI: 1 critical, 0 high, 1 medium and 0 low, plus 3 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is distributed's Vulert package health score?

Vulert scores distributed 76/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of distributed affected?

No. 2026.8.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of distributed should I use?

2026.8.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does distributed have?

5 vulnerabilities are recorded for distributed in the PyPI ecosystem: 1 critical, 0 high, 1 medium and 0 low, plus 3 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new distributed vulnerabilities disclosed?

2 vulnerabilities were recorded for distributed in the last 12 months, and the oldest entry in this database dates to 26 Oct 2021. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of distributed are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

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.