VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

locust: vulnerability history, versions and safety

locust is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 0 release, from Nov 2020 to May 2022. 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
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 locust vulnerabilities

Vulert verdict on locust 2.47.0 i

Updated on 23 Oct 2026

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

Package health score 86/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 2.47.0 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 24 May 2022 i
  • Highest CVSS 6.1 i
  • With no published fix 0 i
  • Depended on by 68 packages i
  • Stars 28,228 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence MIT 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 locust, 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
2.47.0 21 Oct 2026 none MIT — Details →
2.46.8.dev58 21 Oct 2026 none MIT — Details →
2.46.8.dev53 18 Oct 2026 none MIT — Details →
2.46.8.dev52 18 Oct 2026 none MIT — Details →
2.46.8.dev50 17 Oct 2026 none MIT — Details →
2.46.8.dev47 17 Oct 2026 none MIT — Details →
2.46.8.dev43 17 Oct 2026 none MIT — Details →
2.46.8.dev34 15 Oct 2026 none MIT — Details →
2.46.8.dev32 15 Oct 2026 none MIT — Details →
2.46.8.dev30 15 Oct 2026 none MIT — Details →
2.46.8.dev24 10 Oct 2026 none MIT — Details →
2.46.8.dev14 10 Oct 2026 none MIT — Details →
2.46.8.dev8 10 Oct 2026 none MIT — Details →
2.46.8.dev6 10 Oct 2026 none MIT — Details →
2.46.7 04 Oct 2026 none MIT — Details →
2.46.7.dev24 04 Oct 2026 none MIT — Details →
2.46.7.dev22 03 Oct 2026 none MIT — Details →
2.46.7.dev21 03 Oct 2026 none MIT — Details →
2.46.7.dev19 03 Oct 2026 none MIT — Details →
2.46.7.dev17 03 Oct 2026 none MIT — Details →
2.46.7.dev13 03 Oct 2026 none MIT — Details →
2.46.7.dev11 03 Oct 2026 none MIT — Details →
2.46.7.dev9 03 Oct 2026 none MIT — Details →
2.46.7.dev7 26 Sep 2026 none MIT — Details →
2.46.7.dev2 17 Sep 2026 none MIT — Details →
2.46.6 17 Sep 2026 none MIT — Details →
2.46.6.dev12 17 Sep 2026 none MIT — Details →
2.46.6.dev10 15 Sep 2026 none MIT — Details →
2.46.6.dev8 15 Sep 2026 none MIT — Details →
2.46.6.dev4 14 Sep 2026 none MIT — Details →
2.46.6.dev2 13 Sep 2026 none MIT — Details →
2.46.5 07 Sep 2026 none MIT — Details →
2.46.5.dev8 07 Sep 2026 none MIT — Details →
2.46.5.dev6 06 Sep 2026 none MIT — Details →
2.46.5.dev5 26 Aug 2026 none MIT — Details →
2.46.5.dev4 26 Aug 2026 none MIT — Details →
2.46.4 24 Aug 2026 none MIT — Details →
2.46.5.dev2 24 Aug 2026 none MIT — Details →
2.46.4.dev22 21 Aug 2026 none MIT — Details →
2.46.4.dev18 20 Aug 2026 none MIT — Details →
2.46.4.dev17 20 Aug 2026 none MIT — Details →
2.46.4.dev15 20 Aug 2026 none MIT — Details →
2.46.4.dev9 19 Aug 2026 none MIT — Details →
2.46.3 01 Aug 2026 none MIT — Details →
2.46.3.dev9 01 Aug 2026 none MIT — Details →
2.46.3.dev7 01 Aug 2026 none MIT — Details →
2.46.3.dev4 29 Jul 2026 none MIT — Details →
2.46.2 24 Jul 2026 none MIT — Details →
2.46.2.dev20 24 Jul 2026 none MIT — Details →
2.46.2.dev18 24 Jul 2026 none MIT — Details →
2.46.2.dev16 24 Jul 2026 none MIT — Details →
2.46.2.dev14 24 Jul 2026 none MIT — Details →
2.46.2.dev12 24 Jul 2026 none MIT — Details →
2.46.2.dev10 24 Jul 2026 none MIT — Details →
2.46.2.dev6 22 Jul 2026 none MIT — Details →
2.46.2.dev5 21 Jul 2026 none MIT — Details →
2.46.1 21 Jul 2026 none MIT — Details →
2.46.1.dev16 20 Jul 2026 none MIT — Details →
2.46.1.dev14 20 Jul 2026 none MIT — Details →
2.46.1.dev13 20 Jul 2026 none MIT — Details →
2.46.1.dev11 20 Jul 2026 none MIT — Details →
2.46.1.dev5 20 Jul 2026 none MIT — Details →
2.46.1.dev4 19 Jul 2026 none MIT — Details →
2.46.0 19 Jul 2026 none MIT — Details →
2.45.1.dev35 19 Jul 2026 none MIT — Details →
2.45.1.dev33 18 Jul 2026 none MIT — Details →
2.45.1.dev29 14 Jul 2026 none MIT — Details →
2.45.1.dev24 12 Jul 2026 none MIT — Details →
2.45.1.dev22 12 Jul 2026 none MIT — Details →
2.45.1.dev13 09 Jul 2026 none MIT — Details →
2.45.1.dev12 09 Jul 2026 none MIT — Details →
2.45.1.dev11 09 Jul 2026 none MIT — Details →
2.45.1.dev8 09 Jul 2026 none MIT — Details →
2.45.1.dev7 09 Jul 2026 none MIT — Details →
2.45.1.dev5 09 Jul 2026 none MIT — Details →
2.45.1.dev4 09 Jul 2026 none MIT — Details →
2.45.1.dev2 09 Jul 2026 none MIT — Details →
2.45.1.dev1 09 Jul 2026 none MIT — Details →
2.45.0 09 Jul 2026 none MIT — Details →
2.44.5.dev32 09 Jul 2026 none MIT — Details →
2.44.5.dev24 08 Jul 2026 none MIT — Details →
2.44.5.dev23 08 Jul 2026 none MIT — Details →
2.44.5.dev21 08 Jul 2026 none MIT — Details →
2.44.5.dev20 08 Jul 2026 none MIT — Details →
2.44.5.dev19 08 Jul 2026 none MIT — Details →
2.44.5.dev15 08 Jul 2026 none MIT — Details →
2.44.5.dev11 08 Jul 2026 none MIT — Details →
2.44.5.dev9 08 Jul 2026 none MIT — Details →
2.44.5.dev7 08 Jul 2026 none MIT — Details →
2.44.5.dev5 30 Jun 2026 none MIT — Details →
2.44.5.dev3 29 Jun 2026 none MIT — Details →
2.44.5.dev2 26 Jun 2026 none MIT — Details →
2.44.4 18 Jun 2026 none MIT — Details →
2.44.4.dev8 18 Jun 2026 none MIT — Details →
2.44.4.dev5 18 Jun 2026 none MIT — Details →
2.44.4.dev3 16 Jun 2026 none MIT — Details →
2.44.4.dev2 16 Jun 2026 none MIT — Details →
2.44.3 12 Jun 2026 none MIT — Details →
2.44.3.dev1 12 Jun 2026 none MIT — Details →
2.44.2.dev6 11 Jun 2026 none MIT — Details →
2.44.2.dev2 06 Jun 2026 none — — Details →
2.44.1 01 Jun 2026 none — — Details →
2.44.1.dev39 01 Jun 2026 none — — Details →
2.44.1.dev38 01 Jun 2026 none — — Details →
2.44.1.dev36 01 Jun 2026 none — — Details →
2.44.1.dev35 31 May 2026 none — — Details →
2.44.1.dev34 31 May 2026 none — — Details →
2.44.1.dev20 19 May 2026 none — — Details →
2.44.1.dev19 19 May 2026 none — — Details →
2.44.1.dev18 18 May 2026 none — — Details →
2.44.1.dev17 18 May 2026 none — — Details →
2.44.1.dev6 15 May 2026 none — — Details →
2.44.1.dev3 12 May 2026 none — — Details →
2.44.1.dev2 12 May 2026 none — — Details →
2.44.0 11 May 2026 none — — Details →
2.43.5.dev31 11 May 2026 none — — Details →
2.43.5.dev25 09 May 2026 none — — Details →
2.43.5.dev21 09 May 2026 none — — Details →
2.43.5.dev19 08 May 2026 none — — Details →
2.43.5.dev13 03 May 2026 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1
  • 2022 1

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 locust

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-28364: Locust Stored Cross-site Scripting Vulnerability 6.1 medium 1.3.2 24 May 2022
CVE-2020-28364: Stored Cross-Site Scripting (XSS) in Locust N/A unrated 1.3.2 09 Nov 2020

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 locust

Is locust safe to use?

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

Vulert scores locust 86/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 locust affected?

No. 2.47.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.

How many vulnerabilities does locust have?

2 vulnerabilities are recorded for locust 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 locust vulnerabilities disclosed?

0 vulnerabilities were recorded for locust in the last 12 months, and the oldest entry in this database dates to 09 Nov 2020. 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 locust 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 locust for upcoming vulnerabilities?

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