VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

deepspeed: vulnerability history, versions and safety

deepspeed is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 80 releases, first recorded in Oct 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all deepspeed vulnerabilities

Vulert verdict on deepspeed 0.19.8 i

Updated on 23 Oct 2026

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

Package health score 90/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Active

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

  • Current release 0.19.8 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 08 Oct 2024 i
  • Highest CVSS 8.4 i
  • With no published fix 0 i
  • Depended on by 89 packages i
  • Stars 43,251 i
  • Last release this month i
  • Licence Apache-2.0 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 deepspeed, 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
0.19.8 20 Oct 2026 none Apache-2.0 — Details →
0.19.7 16 Sep 2026 none Apache-2.0 — Details →
0.19.6 27 Aug 2026 none Apache-2.0 — Details →
0.19.5 10 Aug 2026 none Apache-2.0 — Details →
0.19.4 06 Aug 2026 none Apache-2.0 — Details →
0.19.3 23 Jul 2026 none Apache-2.0 — Details →
0.19.2 16 Jun 2026 none Apache-2.0 — Details →
0.19.1 30 May 2026 none Apache-2.0 — Details →
0.19.0 06 May 2026 none Apache-2.0 — Details →
0.18.9 30 Mar 2026 none Apache-2.0 — Details →
0.18.8 13 Mar 2026 none Apache-2.0 — Details →
0.18.7 05 Mar 2026 none Apache-2.0 — Details →
0.18.6 12 Feb 2026 none Apache-2.0 — Details →
0.18.5 30 Jan 2026 none Apache-2.0 — Details →
0.18.4 07 Jan 2026 none Apache-2.0 — Details →
0.18.3 09 Dec 2025 none Apache-2.0 — Details →
0.18.2 05 Nov 2025 none Apache-2.0 — Details →
0.18.1 23 Oct 2025 none Apache-2.0 — Details →
0.18.0 07 Oct 2025 none Apache-2.0 — Details →
0.17.6 19 Sep 2025 none Apache-2.0 — Details →
0.17.5 20 Aug 2025 none Apache-2.0 — Details →
0.17.4 31 Jul 2025 none Apache-2.0 — Details →
0.17.3 28 Jul 2025 none Apache-2.0 — Details →
0.17.2 07 Jul 2025 none Apache-2.0 — Details →
0.17.1 09 Jun 2025 none Apache-2.0 — Details →
0.17.0 02 Jun 2025 none Apache-2.0 — Details →
0.16.9 22 May 2025 none Apache-2.0 — Details →
0.16.8 19 May 2025 none Apache-2.0 — Details →
0.16.7 18 Apr 2025 none Apache-2.0 — Details →
0.16.6 16 Apr 2025 none Apache-2.0 — Details →
0.16.5 27 Mar 2025 none Apache-2.0 — Details →
0.16.4 20 Feb 2025 none Apache-2.0 — Details →
0.16.3 21 Jan 2025 none Apache-2.0 — Details →
0.16.2 18 Dec 2024 none Apache-2.0 — Details →
0.16.1 05 Dec 2024 none Apache-2.0 — Details →
0.16.0 25 Nov 2024 none Apache-2.0 — Details →
0.15.4 08 Nov 2024 none Apache-2.0 — Details →
0.15.3 22 Oct 2024 none Apache-2.0 — Details →
0.15.2 09 Oct 2024 none Apache-2.0 — Details →
0.15.1 05 Sep 2024 none Apache-2.0 — Details →
0.15.0 22 Aug 2024 H1 U1 Apache-2.0 Yes Details →
0.14.5 15 Aug 2024 H1 U1 Apache-2.0 Yes Details →
0.14.4 21 Jun 2024 H1 U1 Apache-2.0 Yes Details →
0.14.3 12 Jun 2024 H1 U1 Apache-2.0 Yes Details →
0.14.2 23 Apr 2024 H1 U1 Apache-2.0 Yes Details →
0.14.1 15 Apr 2024 H1 U1 Apache-2.0 Yes Details →
0.14.0 08 Mar 2024 H1 U1 Apache-2.0 Yes Details →
0.13.5 06 Mar 2024 H1 U1 Apache-2.0 Yes Details →
0.13.4 26 Feb 2024 H1 U1 Apache-2.0 Yes Details →
0.13.3 23 Feb 2024 H1 U1 Apache-2.0 Yes Details →
0.13.2 12 Feb 2024 H1 U1 Apache-2.0 Yes Details →
0.13.1 23 Jan 2024 H1 U1 Apache-2.0 Yes Details →
0.13.0 19 Jan 2024 H1 U1 Apache-2.0 Yes Details →
0.12.6 21 Dec 2023 H1 U1 Apache-2.0 Yes Details →
0.12.5 16 Dec 2023 H1 U1 Apache-2.0 Yes Details →
0.12.4 01 Dec 2023 H1 U1 Apache-2.0 Yes Details →
0.12.3 13 Nov 2023 H1 U1 Apache-2.0 Yes Details →
0.12.2 04 Nov 2023 H1 U1 Apache-2.0 Yes Details →
0.12.1 04 Nov 2023 H1 U1 Apache-2.0 Yes Details →
0.12.0 03 Nov 2023 H1 U1 Apache-2.0 Yes Details →
0.11.2 03 Nov 2023 H1 U1 Apache-2.0 Yes Details →
0.11.1 09 Oct 2023 H1 U1 Apache-2.0 Yes Details →
0.11.0 06 Oct 2023 H1 U1 Apache-2.0 Yes Details →
0.10.3 11 Sep 2023 H1 U1 Apache-2.0 Yes Details →
0.10.2 31 Aug 2023 H1 U1 Apache-2.0 Yes Details →
0.10.1 18 Aug 2023 H1 U1 Apache-2.0 Yes Details →
0.10.0 17 Jul 2023 H1 U1 Apache-2.0 Yes Details →
0.9.5 22 Jun 2023 H1 U1 Apache-2.0 Yes Details →
0.9.4 09 Jun 2023 H1 U1 Apache-2.0 Yes Details →
0.9.3 02 Jun 2023 H1 U1 Apache-2.0 Yes Details →
0.9.2 03 May 2023 H1 U1 MIT Yes Details →
0.9.1 21 Apr 2023 H1 U1 MIT Yes Details →
0.9.0 13 Apr 2023 H1 U1 MIT Yes Details →
0.8.3 20 Mar 2023 H1 U1 MIT Yes Details →
0.8.2 07 Mar 2023 H1 U1 MIT Yes Details →
0.8.1 17 Feb 2023 H1 U1 MIT Yes Details →
0.8.0 17 Jan 2023 H1 U1 MIT Yes Details →
0.7.7 12 Dec 2022 H1 U1 MIT Yes Details →
0.7.6 01 Dec 2022 H1 U1 MIT Yes Details →
0.7.5 14 Nov 2022 H1 U1 MIT Yes Details →
0.7.4 21 Oct 2022 H1 U1 MIT Yes Details →
0.7.3 19 Sep 2022 H1 U1 MIT Yes Details →
0.7.2 25 Aug 2022 H1 U1 MIT Yes Details →
0.7.1 23 Aug 2022 H1 U1 MIT Yes Details →
0.7.0 01 Aug 2022 H1 U1 MIT Yes Details →
0.6.7 19 Jul 2022 H1 U1 MIT Yes Details →
0.6.6 18 Jul 2022 H1 U1 MIT Yes Details →
0.6.5 25 May 2022 H1 U1 MIT Yes Details →
0.6.4 06 May 2022 H1 U1 MIT Yes Details →
0.6.3 27 Apr 2022 H1 U1 MIT Yes Details →
0.6.1 28 Mar 2022 H1 U1 MIT Yes Details →
0.6.0 07 Mar 2022 H1 U1 MIT Yes Details →
0.5.10 19 Jan 2022 H1 U1 MIT Yes Details →
0.5.9 04 Jan 2022 H1 U1 MIT Yes Details →
0.5.8 01 Dec 2021 H1 U1 MIT Yes Details →
0.5.7 20 Nov 2021 H1 U1 MIT Yes Details →
0.5.6 11 Nov 2021 H1 U1 MIT Yes Details →
0.5.5 02 Nov 2021 H1 U1 MIT Yes Details →
0.5.4 06 Oct 2021 H1 U1 MIT Yes Details →
0.5.3 16 Sep 2021 H1 U1 MIT Yes Details →
0.5.2 14 Sep 2021 H1 U1 — Yes Details →
0.5.1 26 Aug 2021 H1 U1 — Yes Details →
0.5.0 17 Aug 2021 H1 U1 — Yes Details →
0.4.5 10 Aug 2021 H1 U1 — Yes Details →
0.4.4 30 Jul 2021 H1 U1 — Yes Details →
0.4.3 12 Jul 2021 H1 U1 — Yes Details →
0.4.2 01 Jul 2021 H1 U1 — Yes Details →
0.4.1 23 Jun 2021 H1 U1 — Yes Details →
0.4.0 08 Jun 2021 H1 U1 — Yes Details →
0.3.16 30 Apr 2021 H1 U1 — Yes Details →
0.3.15 19 Apr 2021 H1 U1 — Yes Details →
0.3.14 08 Apr 2021 H1 U1 — Yes Details →
0.3.13 16 Mar 2021 H1 U1 — Yes Details →
0.3.12 12 Mar 2021 H1 U1 — Yes Details →
0.3.11 02 Feb 2021 H1 U1 — Yes Details →
0.3.10 08 Jan 2021 H1 U1 — Yes Details →
0.3.9 23 Dec 2020 H1 U1 — Yes Details →
0.3.8 09 Dec 2020 H1 U1 — Yes Details →
0.3.7 25 Nov 2020 H1 U1 — Yes Details →
0.3.6 25 Nov 2020 H1 U1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 2

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

03 Vulnerabilities

Recorded vulnerabilities for deepspeed

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-43497: DeepSpeed Remote Code Execution Vulnerability 8.4 high 0.15.1 08 Oct 2024
CVE-2024-43497: DeepSpeed Remote Code Execution Vulnerability 7.8 high 0.15.1 08 Oct 2024

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 deepspeed

Is deepspeed safe to use?

Vulert records 2 vulnerabilities for deepspeed in PyPI: 0 critical, 1 high, 0 medium and 0 low, plus 1 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 deepspeed's Vulert package health score?

Vulert scores deepspeed 90/100, which reads as healthy. 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 deepspeed affected?

No. 0.19.8, 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.

How many vulnerabilities does deepspeed have?

2 vulnerabilities are recorded for deepspeed in the PyPI ecosystem: 0 critical, 1 high, 0 medium and 0 low, plus 1 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 deepspeed vulnerabilities disclosed?

0 vulnerabilities were recorded for deepspeed in the last 12 months, and the oldest entry in this database dates to 08 Oct 2024. 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 deepspeed 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 deepspeed for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the deepspeed version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.