VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

accelerate: vulnerability history, versions and safety

accelerate is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 83 releases, from Aug 2026 to Sep 2026. 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 M1 U1
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
2 in the last 12 months

Most recent disclosure 10 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all accelerate vulnerabilities

Vulert verdict on accelerate 1.15.0 i

Updated on 23 Oct 2026

Careful: 1.15.0 has 2 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 1.15.0 — affected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 10 Sep 2026 i
  • Highest CVSS 7.1 i
  • With no published fix 2 i
  • Depended on by 3,063 packages i
  • Stars 9,923 i
  • OpenSSF scorecard 5/10 i
  • Last release 1 month ago i
  • Licence non-standard 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 accelerate, 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
1.15.0 09 Sep 2026 M1 U1 non-standard No Details →
1.14.0 11 Jun 2026 M1 U1 non-standard No Details →
1.13.0 04 Mar 2026 M1 U1 non-standard No Details →
1.12.0 21 Nov 2025 M1 U1 non-standard No Details →
1.11.0 20 Oct 2025 M1 U1 non-standard No Details →
1.10.1 25 Aug 2025 M1 U1 non-standard No Details →
1.10.0 07 Aug 2025 M1 U1 non-standard No Details →
1.9.0 16 Jul 2025 M1 U1 non-standard No Details →
1.8.1 20 Jun 2025 M1 U1 non-standard No Details →
1.8.0 19 Jun 2025 M1 U1 non-standard No Details →
1.7.0 15 May 2025 M1 U1 non-standard No Details →
1.6.0 01 Apr 2025 M1 U1 non-standard No Details →
1.5.2 14 Mar 2025 M1 U1 non-standard No Details →
1.5.1 12 Mar 2025 M1 U1 non-standard No Details →
1.5.0 12 Mar 2025 M1 U1 non-standard No Details →
1.4.0 17 Feb 2025 M1 U1 non-standard No Details →
1.3.0 17 Jan 2025 M1 U1 non-standard No Details →
1.2.1 13 Dec 2024 M1 U1 non-standard No Details →
1.2.0 06 Dec 2024 M1 U1 non-standard No Details →
1.1.1 07 Nov 2024 M1 U1 non-standard No Details →
1.1.0 01 Nov 2024 M1 U1 non-standard No Details →
1.0.1 12 Oct 2024 M1 U1 non-standard No Details →
1.0.0 07 Oct 2024 M1 U1 non-standard No Details →
1.0.0rc1 13 Sep 2024 M1 U1 non-standard No Details →
1.0.0rc0 13 Sep 2024 M1 U1 non-standard No Details →
0.34.2 05 Sep 2024 M1 U1 non-standard No Details →
0.34.1 05 Sep 2024 M1 U1 non-standard No Details →
0.34.0 02 Sep 2024 M1 U1 non-standard No Details →
0.33.0 23 Jul 2024 M1 U1 non-standard No Details →
0.32.1 04 Jul 2024 M1 U1 non-standard No Details →
0.32.0 03 Jul 2024 M1 U1 non-standard No Details →
0.31.0 07 Jun 2024 M1 U1 non-standard No Details →
0.30.1 10 May 2024 M1 U1 non-standard No Details →
0.30.0 03 May 2024 M1 U1 non-standard No Details →
0.30.0rc0 03 May 2024 M1 U1 non-standard No Details →
0.29.3 17 Apr 2024 M1 U1 non-standard No Details →
0.29.2 09 Apr 2024 M1 U1 non-standard No Details →
0.29.1 05 Apr 2024 M1 U1 non-standard No Details →
0.29.0 05 Apr 2024 M1 U1 non-standard No Details →
0.28.0 12 Mar 2024 M1 U1 non-standard No Details →
0.27.2 13 Feb 2024 M1 U1 non-standard No Details →
0.27.1 13 Feb 2024 M1 U1 non-standard No Details →
0.27.0 09 Feb 2024 M1 U1 non-standard No Details →
0.26.1 11 Jan 2024 M1 U1 non-standard No Details →
0.26.0 10 Jan 2024 M1 U1 non-standard No Details →
0.25.0 01 Dec 2023 M1 U1 non-standard No Details →
0.24.1 30 Oct 2023 M1 U1 non-standard No Details →
0.24.0 24 Oct 2023 M1 U1 non-standard No Details →
0.23.0 14 Sep 2023 M1 U1 non-standard No Details →
0.22.0 23 Aug 2023 M1 U1 non-standard No Details →
0.21.0 13 Jul 2023 M1 U1 non-standard No Details →
0.20.3 08 Jun 2023 M1 U1 non-standard No Details →
0.20.2 08 Jun 2023 M1 U1 non-standard No Details →
0.20.1 07 Jun 2023 M1 U1 non-standard No Details →
0.20.0 07 Jun 2023 M1 U1 non-standard No Details →
0.19.0 08 May 2023 M1 U1 non-standard No Details →
0.18.0 24 Mar 2023 M1 U1 non-standard No Details →
0.17.1 13 Mar 2023 M1 U1 non-standard No Details →
0.17.0 09 Mar 2023 M1 U1 non-standard No Details →
0.16.0 31 Jan 2023 M1 U1 non-standard No Details →
0.15.0 01 Dec 2022 M1 U1 non-standard No Details →
0.14.0 08 Nov 2022 M1 U1 non-standard No Details →
0.13.2 17 Oct 2022 M1 U1 non-standard No Details →
0.13.1 07 Oct 2022 M1 U1 non-standard No Details →
0.13.0 05 Oct 2022 M1 U1 non-standard No Details →
0.12.0 04 Aug 2022 M1 U1 non-standard No Details →
0.11.0 18 Jul 2022 M1 U1 non-standard No Details →
0.10.0 15 Jun 2022 M1 U1 non-standard No Details →
0.9.0 20 May 2022 M1 U1 non-standard No Details →
0.8.0 12 May 2022 M1 U1 non-standard No Details →
0.7.1 29 Apr 2022 M1 U1 non-standard No Details →
0.7.0 28 Apr 2022 M1 U1 non-standard No Details →
0.6.2 31 Mar 2022 M1 U1 non-standard No Details →
0.6.1 18 Mar 2022 M1 U1 non-standard No Details →
0.6.0 18 Mar 2022 M1 U1 non-standard No Details →
0.5.1 27 Sep 2021 M1 U1 non-standard No Details →
0.5.0 23 Sep 2021 M1 U1 non-standard No Details →
0.4.0 10 Aug 2021 M1 U1 non-standard No Details →
0.3.0 29 Apr 2021 M1 U1 non-standard No Details →
0.2.1 19 Apr 2021 M1 U1 non-standard No Details →
0.2.0 15 Apr 2021 M1 U1 non-standard No Details →
0.1.0 05 Mar 2021 M1 U1 non-standard No Details →
0.0.1 30 Oct 2020 M1 U1 non-standard No Details →

All 83 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for accelerate

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-69112: Hugging Face Accelerate Path Traversal and Denial of Service Vulnerability 7.1 medium No fix published 10 Aug 2026
CVE-2026-69112: Hugging Face Accelerate Path Traversal and Denial of Service Vulnerability 7.1 high No fix published 10 Sep 2026

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 accelerate

Is accelerate safe to use?

Vulert records 2 vulnerabilities for accelerate in PyPI: 0 critical, 0 high, 1 medium and 0 low, plus 1 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is accelerate's Vulert package health score?

Vulert scores accelerate 60/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of accelerate affected?

Yes. 1.15.0, the version you would install today, has 2 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of accelerate should I use?

1.15.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 accelerate have?

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

2 vulnerabilities were recorded for accelerate in the last 12 months, and the oldest entry in this database dates to 10 Aug 2026. 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 accelerate 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 accelerate for upcoming vulnerabilities?

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