VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

lodash: vulnerability history, versions and safety

lodash is a package in the npm ecosystem. Vulert records 11 vulnerabilities for it across 117 releases, from Jul 2018 to Apr 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
11 vulnerabilities recorded C1 H4 M5 L1
i
1 with no fix published

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

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

Most recent disclosure 01 Apr 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all lodash vulnerabilities

Vulert verdict on lodash 4.18.1 i

Updated on 23 Oct 2026

Careful: 4.18.1 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 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 4.18.1 — affected i
  • Vulnerabilities on record 11 over 7 years · 3 in the last year i
  • Latest disclosure 01 Apr 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 1 i
  • Depended on by 701,344 packages i
  • Stars 61,291 i
  • OpenSSF scorecard 5/10 i
  • Last release 6 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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 lodash, 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
4.18.1 01 Apr 2026 L1 MIT No Details →
4.18.0 31 Mar 2026 L1 MIT No Details →
4.17.23 21 Jan 2026 H1 M1 L1 MIT No Details →
4.17.21 20 Feb 2021 H1 M2 L1 MIT No Details →
4.17.20 13 Aug 2020 H2 M3 L1 MIT No Details →
4.17.19 08 Jul 2020 H2 M3 L1 MIT No Details →
4.17.18 08 Jul 2020 H3 M3 L1 MIT No Details →
4.17.17 08 Jul 2020 H3 M3 L1 MIT No Details →
4.17.16 08 Jul 2020 H3 M3 L1 MIT No Details →
4.17.15 19 Jul 2019 H3 M3 L1 MIT No Details →
4.17.14 10 Jul 2019 H3 M3 L1 MIT No Details →
4.17.13 09 Jul 2019 H3 M3 L1 MIT No Details →
4.17.12 09 Jul 2019 H3 M3 L1 MIT No Details →
4.17.11 12 Sep 2018 C1 H3 M3 L1 MIT No Details →
4.17.10 24 Apr 2018 C1 H4 M4 L1 MIT No Details →
4.17.9 24 Apr 2018 C1 H4 M4 L1 MIT No Details →
4.17.5 04 Feb 2018 C1 H4 M4 L1 MIT No Details →
4.17.4 31 Dec 2016 C1 H4 M5 L1 MIT No Details →
4.17.3 24 Dec 2016 C1 H4 M5 L1 MIT No Details →
4.17.2 16 Nov 2016 C1 H4 M5 L1 MIT No Details →
4.17.1 15 Nov 2016 C1 H4 M5 L1 MIT No Details →
4.17.0 14 Nov 2016 C1 H4 M5 L1 MIT No Details →
4.16.6 01 Nov 2016 C1 H4 M5 L1 MIT No Details →
4.16.5 31 Oct 2016 C1 H4 M5 L1 MIT No Details →
4.16.4 06 Oct 2016 C1 H4 M5 L1 MIT No Details →
4.16.3 03 Oct 2016 C1 H4 M5 L1 MIT No Details →
4.16.2 26 Sep 2016 C1 H4 M5 L1 MIT No Details →
4.16.1 20 Sep 2016 C1 H4 M5 L1 MIT No Details →
4.16.0 19 Sep 2016 C1 H4 M5 L1 MIT No Details →
4.15.0 12 Aug 2016 C1 H4 M5 L1 MIT No Details →
4.14.2 08 Aug 2016 C1 H4 M5 L1 MIT No Details →
4.14.1 29 Jul 2016 C1 H4 M5 L1 MIT No Details →
4.14.0 24 Jul 2016 C1 H4 M5 L1 MIT No Details →
4.13.1 23 May 2016 C1 H4 M5 L1 MIT No Details →
4.13.0 23 May 2016 C1 H4 M5 L1 MIT No Details →
4.12.0 08 May 2016 C1 H4 M5 L1 MIT No Details →
4.11.2 02 May 2016 C1 H4 M5 L1 MIT No Details →
4.11.1 14 Apr 2016 C1 H4 M5 L1 MIT No Details →
4.11.0 13 Apr 2016 C1 H4 M5 L1 MIT No Details →
4.10.0 11 Apr 2016 C1 H4 M5 L1 MIT No Details →
4.9.0 08 Apr 2016 C1 H4 M5 L1 MIT No Details →
4.8.2 05 Apr 2016 C1 H4 M5 L1 MIT No Details →
4.8.1 04 Apr 2016 C1 H4 M5 L1 MIT No Details →
4.8.0 04 Apr 2016 C1 H4 M5 L1 MIT No Details →
4.7.0 31 Mar 2016 C1 H4 M5 L1 MIT No Details →
4.6.1 02 Mar 2016 C1 H4 M5 L1 MIT No Details →
4.6.0 02 Mar 2016 C1 H4 M5 L1 MIT No Details →
4.5.1 22 Feb 2016 C1 H4 M5 L1 MIT No Details →
4.5.0 17 Feb 2016 C1 H4 M5 L1 MIT No Details →
4.4.0 16 Feb 2016 C1 H4 M5 L1 MIT No Details →
4.3.0 08 Feb 2016 C1 H4 M5 L1 MIT No Details →
4.2.1 03 Feb 2016 C1 H4 M5 L1 MIT No Details →
4.2.0 02 Feb 2016 C1 H4 M5 L1 MIT No Details →
4.1.0 29 Jan 2016 C1 H4 M5 L1 MIT No Details →
4.0.1 25 Jan 2016 C1 H4 M5 L1 MIT No Details →
4.0.0 12 Jan 2016 C1 H4 M5 L1 MIT No Details →
3.10.1 04 Aug 2015 C1 H3 M4 L1 MIT No Details →
3.10.0 30 Jun 2015 C1 H3 M4 L1 MIT No Details →
3.9.3 26 May 2015 C1 H3 M4 L1 MIT No Details →
3.9.2 24 May 2015 C1 H3 M4 L1 MIT No Details →
3.9.1 19 May 2015 C1 H3 M4 L1 MIT No Details →
3.9.0 19 May 2015 C1 H3 M4 L1 MIT No Details →
3.8.0 01 May 2015 C1 H3 M4 L1 MIT No Details →
2.4.2 26 Apr 2015 C1 H2 M4 L1 MIT No Details →
3.7.0 16 Apr 2015 C1 H3 M4 L1 MIT No Details →
1.0.2 30 Mar 2015 C1 H2 M4 L1 MIT No Details →
3.6.0 25 Mar 2015 C1 H2 M4 L1 MIT No Details →
3.5.0 09 Mar 2015 C1 H2 M4 L1 MIT No Details →
3.4.0 06 Mar 2015 C1 H2 M4 L1 MIT No Details →
3.3.1 24 Feb 2015 C1 H2 M4 L1 MIT No Details →
3.3.0 20 Feb 2015 C1 H2 M4 L1 MIT No Details →
3.2.0 12 Feb 2015 C1 H2 M4 L1 MIT No Details →
3.1.0 03 Feb 2015 C1 H2 M4 L1 MIT No Details →
3.0.1 30 Jan 2015 C1 H2 M4 L1 MIT No Details →
3.0.0 26 Jan 2015 C1 H2 M4 L1 MIT No Details →
2.4.1 03 Dec 2013 C1 H2 M4 L1 MIT No Details →
2.4.0 26 Nov 2013 C1 H2 M4 L1 MIT No Details →
2.3.0 11 Nov 2013 C1 H2 M4 L1 MIT No Details →
2.2.1 03 Oct 2013 C1 H2 M4 L1 MIT No Details →
2.2.0 29 Sep 2013 C1 H2 M4 L1 MIT No Details →
2.1.0 23 Sep 2013 C1 H2 M4 L1 MIT No Details →
2.0.0 14 Sep 2013 C1 H2 M4 L1 MIT No Details →
1.3.1 04 Sep 2013 C1 H2 M4 L1 MIT No Details →
1.3.0 04 Sep 2013 C1 H2 M4 L1 MIT No Details →
1.2.1 04 Sep 2013 C1 H2 M4 L1 MIT No Details →
1.2.0 04 Sep 2013 C1 H2 M4 L1 MIT No Details →
1.1.1 04 Sep 2013 C1 H2 M4 L1 MIT No Details →
1.1.0 04 Sep 2013 C1 H2 M4 L1 MIT No Details →
1.0.1 31 Aug 2013 C1 H2 M4 L1 MIT No Details →
1.0.0 31 Aug 2013 C1 H2 M4 L1 MIT No Details →
1.0.0-rc.3 31 Aug 2013 C1 H2 M4 L1 MIT No Details →
1.0.0-rc.2 31 Aug 2013 C1 H2 M4 L1 MIT No Details →
1.0.0-rc.1 31 Aug 2013 C1 H2 M4 L1 MIT No Details →
0.10.0 31 Aug 2013 C1 H2 M4 L1 MIT No Details →
0.9.2 31 Aug 2013 C1 H2 M4 L1 MIT No Details →
0.9.1 31 Aug 2013 C1 H2 M4 L1 MIT No Details →
0.9.0 31 Aug 2013 C1 H2 M4 L1 MIT No Details →
0.8.2 10 Oct 2012 C1 H2 M4 L1 MIT No Details →
0.8.1 04 Oct 2012 C1 H2 M4 L1 MIT No Details →
0.8.0 02 Oct 2012 C1 H2 M4 L1 MIT No Details →
0.7.0 11 Sep 2012 C1 H2 M4 L1 — No Details →
0.6.1 30 Aug 2012 C1 H2 M4 L1 — No Details →
0.6.0 28 Aug 2012 C1 H2 M4 L1 — No Details →
0.5.2 22 Aug 2012 C1 H2 M4 L1 — No Details →
0.5.1 18 Aug 2012 C1 H2 M4 L1 — No Details →
0.5.0 17 Aug 2012 C1 H2 M4 L1 — No Details →
0.5.0-rc.1 07 Aug 2012 C1 H2 M4 L1 — No Details →
0.4.2 16 Jul 2012 C1 H2 M4 L1 — No Details →
0.4.1 12 Jul 2012 C1 H2 M4 L1 — No Details →
0.4.0 11 Jul 2012 C1 H2 M4 L1 — No Details →
0.3.2 14 Jun 2012 C1 H2 M4 L1 — No Details →
0.3.1 11 Jun 2012 C1 H2 M4 L1 — No Details →
0.3.0 06 Jun 2012 C1 H2 M4 L1 — No Details →
0.2.2 30 May 2012 C1 H2 M4 L1 — No Details →
0.2.1 24 May 2012 C1 H2 M4 L1 — No Details →
0.2.0 22 May 2012 C1 H2 M4 L1 — No Details →
0.1.0 23 Apr 2012 C1 H2 M4 L1 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1
  • 2019 3
  • 2020 1
  • 2021 2
  • 2022 1
  • 2026 3

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

03 Vulnerabilities

Recorded vulnerabilities for lodash

The 5 most severe of 11 vulnerabilities recorded for this package

Search all 11 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2019-10744: Prototype Pollution in lodash 9.1 critical 4.17.12 10 Jul 2019
CVE-2026-4800: lodash Code Injection Vulnerability via `_.template` Imports 8.1 high 4.18.0 01 Apr 2026
CVE-2020-8203: Prototype Pollution in lodash 7.4 high 4.17.19 15 Jul 2020
CVE-2021-23337: Command Injection in lodash 7.2 high 4.17.21 06 May 2021
CVE-2018-3721: Prototype Pollution in lodash 6.5 medium 4.17.5 26 Jul 2018

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 lodash

Is lodash safe to use?

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

What is lodash's Vulert package health score?

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

Yes. 4.18.1, 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 lodash should I use?

4.18.1 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 lodash have?

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

How often are new lodash vulnerabilities disclosed?

3 vulnerabilities were recorded for lodash in the last 12 months, and the oldest entry in this database dates to 26 Jul 2018. 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 lodash 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 lodash for upcoming vulnerabilities?

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