VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

locutus: vulnerability history, versions and safety

locutus is a package in the npm ecosystem. Vulert records 8 vulnerabilities for it across 63 releases, from May 2021 to Mar 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
8 vulnerabilities recorded C4 H2 M2
i
1 with no fix published

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

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

Most recent disclosure 27 Mar 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all locutus vulnerabilities

Vulert verdict on locutus 3.0.36 i

Updated on 23 Oct 2026

Careful: 3.0.36 has 1 known vulnerability, and 1 has 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 Widely used
  • 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 3.0.36 — affected i
  • Vulnerabilities on record 8 over 4 years · 5 in the last year i
  • Latest disclosure 27 Mar 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 1 i
  • Depended on by 94 packages i
  • Stars 3,760 i
  • OpenSSF scorecard 3/10 i
  • Last release 5 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, 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 locutus, 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
3.0.36 16 May 2026 C1 MIT No Details →
3.0.35 15 May 2026 C1 MIT No Details →
3.0.34 30 Mar 2026 C1 MIT No Details →
3.0.33 30 Mar 2026 C1 MIT No Details →
3.0.32 27 Mar 2026 C1 MIT No Details →
3.0.31 27 Mar 2026 C1 MIT No Details →
3.0.30 26 Mar 2026 C1 MIT No Details →
3.0.28 26 Mar 2026 C1 MIT No Details →
3.0.27 25 Mar 2026 C1 MIT No Details →
3.0.26 25 Mar 2026 C1 MIT No Details →
3.0.25 25 Mar 2026 C1 MIT No Details →
3.0.24 16 Mar 2026 C1 M2 MIT No Details →
3.0.23 16 Mar 2026 C1 M2 MIT No Details →
3.0.22 16 Mar 2026 C1 M2 MIT No Details →
3.0.21 16 Mar 2026 C1 M2 MIT No Details →
3.0.20 15 Mar 2026 C1 M2 MIT No Details →
3.0.19 15 Mar 2026 C1 M2 MIT No Details →
3.0.18 14 Mar 2026 C1 M2 MIT No Details →
3.0.17 14 Mar 2026 C1 M2 MIT No Details →
3.0.16 13 Mar 2026 C1 M2 MIT No Details →
3.0.15 13 Mar 2026 C1 M2 MIT No Details →
3.0.14 11 Mar 2026 C1 M2 MIT No Details →
3.0.13 11 Mar 2026 C2 M2 MIT No Details →
3.0.12 11 Mar 2026 C2 M2 MIT No Details →
3.0.11 10 Mar 2026 C2 M2 MIT No Details →
3.0.10 09 Mar 2026 C2 M2 MIT No Details →
3.0.9 06 Mar 2026 C2 M2 MIT No Details →
3.0.8 06 Mar 2026 C2 M2 MIT No Details →
3.0.7 05 Mar 2026 C2 M2 MIT No Details →
3.0.5 04 Mar 2026 C2 M2 MIT No Details →
3.0.4 04 Mar 2026 C2 M2 MIT No Details →
3.0.3 04 Mar 2026 C2 M2 MIT No Details →
3.0.2 03 Mar 2026 C2 M2 MIT No Details →
3.0.1 03 Mar 2026 C2 M2 MIT No Details →
3.0.0 03 Mar 2026 C2 M2 MIT No Details →
2.0.39 02 Feb 2026 C2 H1 M2 MIT No Details →
2.0.38 19 Jan 2026 C3 H1 M1 MIT No Details →
2.0.37 08 Jan 2026 C3 H1 M1 MIT No Details →
2.0.36 08 Jan 2026 C3 H1 M1 MIT No Details →
2.0.35 08 Jan 2026 C3 H1 M1 MIT No Details →
2.0.34 08 Jan 2026 C3 H1 M1 MIT No Details →
2.0.32 06 Apr 2024 C3 H1 M1 MIT No Details →
2.0.31 05 Apr 2024 C3 H1 M1 MIT No Details →
2.0.30 05 Apr 2024 C3 H1 M1 MIT No Details →
2.0.29 04 Apr 2024 C3 H1 M1 MIT No Details →
2.0.16 27 Jan 2022 C3 H1 M1 MIT No Details →
2.0.15 27 May 2021 C3 H1 M1 MIT No Details →
2.0.14 02 Oct 2020 C3 H2 M1 MIT No Details →
2.0.13 02 Oct 2020 C3 H2 M1 MIT No Details →
2.0.12 03 Sep 2020 C3 H2 M1 MIT No Details →
2.0.11 12 Jun 2019 C3 H2 M1 MIT No Details →
2.0.10 07 Sep 2018 C3 H2 M1 MIT No Details →
2.0.9 22 Jun 2017 C3 H2 M1 MIT No Details →
2.0.8 23 Feb 2017 C3 H2 M1 MIT No Details →
2.0.7 09 Feb 2017 C3 H2 M1 MIT No Details →
2.0.6 08 Nov 2016 C3 H2 M1 MIT No Details →
2.0.5 16 Jun 2016 C3 H2 M1 MIT No Details →
2.0.4 25 May 2016 C3 H2 M1 MIT No Details →
2.0.3 22 May 2016 C3 H2 M1 MIT No Details →
2.0.2 02 May 2016 C3 H2 M1 MIT No Details →
2.0.1 02 May 2016 C3 H2 M1 MIT No Details →
2.0.0 02 May 2016 C3 H2 M1 MIT No Details →
0.0.1 18 Apr 2016 C3 H2 M1 MIT No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 3
  • 2026 5

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

03 Vulnerabilities

Recorded vulnerabilities for locutus

The 5 most severe of 8 vulnerabilities recorded for this package

Search all 8 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-7719: Prototype Pollution in locutus 9.8 critical 2.0.12 06 May 2021
CVE-2020-13619: OS Command Injection in Locutus 9.8 critical No fix published 26 Jul 2021
CVE-2026-32304: Locutus Package Vulnerable to RCE via Unsanitized Input in create_function() 9.8 critical 3.0.14 13 Mar 2026
Critical Prototype Pollution Vulnerability in locutus Package 9.4 critical 2.0.39 02 Feb 2026
CVE-2026-29091: locutus Remote Code Execution Vulnerability in call_user_func_array 8.1 high 3.0.0 04 Mar 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 locutus

Is locutus safe to use?

Vulert records 8 vulnerabilities for locutus in npm: 4 critical, 2 high, 2 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is locutus's Vulert package health score?

Vulert scores locutus 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 locutus affected?

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

Which version of locutus should I use?

3.0.36 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 locutus have?

8 vulnerabilities are recorded for locutus in the npm ecosystem: 4 critical, 2 high, 2 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new locutus vulnerabilities disclosed?

5 vulnerabilities were recorded for locutus in the last 12 months, and the oldest entry in this database dates to 06 May 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 locutus 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 locutus for upcoming vulnerabilities?

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