VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

node-lodash: vulnerability history, versions and safety

node-lodash is a package in the Debian ecosystem. Vulert records 17 vulnerabilities for it across 21 releases, from Nov -0001 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
17 vulnerabilities recorded U17
i
3 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 31 Mar 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all node-lodash vulnerabilities

Vulert verdict on node-lodash i

Updated on 23 Oct 2026

Careful: 3 of the 17 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 17 vulnerabilities on record across 2026 years, 2 in the last year.

What to do: Plan around the 3 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 17 over 2026 years · 2 in the last year i
  • Latest disclosure 31 Mar 2026 i
  • Highest CVSS 9.1 i
  • With no published fix 3 i

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 holds for node-lodash, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 21 of 21 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 0 1
  • 2018 2
  • 2019 6
  • 2020 2
  • 2021 4
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for node-lodash

The 5 most severe of 17 vulnerabilities recorded for this package

Search all 17 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
Prototype Pollution Vulnerability in Lodash: CVE-2019-10744 9.1 critical 4.17.15+dfsg-1 26 Jul 2019
Critical Code Injection Vulnerability in node-lodash: CVE-2026-4800 8.1 high No fix published 31 Mar 2026
Prototype Pollution Vulnerability in Lodash: CVE-2020-8203 7.4 high 4.17.19+dfsg-1 15 Jul 2020
Command Injection Vulnerability in Lodash Package: CVE-2021-23337 7.2 high 4.17.21+dfsg+~cs8.31.173-1 15 Feb 2021
Open Source Vulnerability in node-lodash: CVE-2018-3721 6.5 medium 4.17.11+dfsg-1 07 Jun 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 node-lodash

Is node-lodash safe to use?

Vulert records 17 vulnerabilities for node-lodash in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 17 not yet rated. 3 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does node-lodash have?

17 vulnerabilities are recorded for node-lodash in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 17 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 node-lodash vulnerabilities disclosed?

2 vulnerabilities were recorded for node-lodash in the last 12 months, and the oldest entry in this database dates to 30 Nov -0001. 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 node-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 node-lodash for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the node-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.