Lodash
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in Lodash.
By the Year
In 2026 there have been 3 vulnerabilities in Lodash with an average score of 7.3 out of ten. Lodash did not have any published security vulnerabilities last year. That is, 3 more vulnerabilities have already been reported in 2026 as compared to last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 3 | 7.30 |
| 2025 | 0 | 0.00 |
| 2024 | 0 | 0.00 |
| 2023 | 0 | 0.00 |
| 2022 | 0 | 0.00 |
| 2021 | 2 | 6.25 |
| 2020 | 1 | 0.00 |
| 2019 | 3 | 7.07 |
| 2018 | 1 | 6.50 |
It may take a day or so for new Lodash vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Lodash Security Vulnerabilities
Lodash <4.18.0 _.template key-names RCE
CVE-2026-4800
8.1 - High
- March 31, 2026
Impact: The fix for CVE-2021-23337 (https://github.com/advisories/GHSA-35jh-r3h4-6jhm) added validation for the variable option in _.template but did not apply the same validation to options.imports key names. Both paths flow into the same Function() constructor sink. When an application passes untrusted input as options.imports key names, an attacker can inject default-parameter expressions that execute arbitrary code at template compilation time. Additionally, _.template uses assignInWith to merge imports, which enumerates inherited properties via for..in. If Object.prototype has been polluted by any other vector, the polluted keys are copied into the imports object and passed to Function(). Patches: Users should upgrade to version 4.18.0. Workarounds: Do not pass untrusted input as key names in options.imports. Only use developer-controlled, static key names.
Code Injection
Prototype Pollution in Lodash 4.17.23 via _.unset/_.omit (CVE-2026-2950)
CVE-2026-2950
6.5 - Medium
- March 31, 2026
Impact: Lodash versions 4.17.23 and earlier are vulnerable to prototype pollution in the _.unset and _.omit functions. The fix for (CVE-2025-13465: https://github.com/lodash/lodash/security/advisories/GHSA-xxjr-mmjv-4gpg) only guards against string key members, so an attacker can bypass the check by passing array-wrapped path segments. This allows deletion of properties from built-in prototypes such as Object.prototype, Number.prototype, and String.prototype. The issue permits deletion of prototype properties but does not allow overwriting their original behavior. Patches: This issue is patched in 4.18.0. Workarounds: None. Upgrade to the patched version.
Prototype Pollution
Prototype Pollution via _.unset/.omit in Lodash 4.17.22
CVE-2025-13465
- January 21, 2026
Lodash versions 4.0.0 through 4.17.22 are vulnerable to prototype pollution in the _.unset and _.omit functions. An attacker can pass crafted paths which cause Lodash to delete methods from global prototypes. The issue permits deletion of properties but does not allow overwriting their original behavior. This issue is patched on 4.17.23
Prototype Pollution
Lodash versions prior to 4.17.21 are vulnerable to Command Injection
CVE-2021-23337
7.2 - High
- February 15, 2021
Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
Code Injection
Lodash versions prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS)
CVE-2020-28500
5.3 - Medium
- February 15, 2021
Lodash versions prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions.
Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20.
CVE-2020-8203
- July 15, 2020
Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20.
Allocation of Resources Without Limits or Throttling
Versions of lodash lower than 4.17.12 are vulnerable to Prototype Pollution
CVE-2019-10744
9.1 - Critical
- July 26, 2019
Versions of lodash lower than 4.17.12 are vulnerable to Prototype Pollution. The function defaultsDeep could be tricked into adding or modifying properties of Object.prototype using a constructor payload.
Prototype Pollution
lodash prior to 4.17.11 is affected by: CWE-400: Uncontrolled Resource Consumption
CVE-2019-1010266
6.5 - Medium
- July 17, 2019
lodash prior to 4.17.11 is affected by: CWE-400: Uncontrolled Resource Consumption. The impact is: Denial of service. The component is: Date handler. The attack vector is: Attacker provides very long strings, which the library attempts to match using a regular expression. The fixed version is: 4.17.11.
Resource Exhaustion
A prototype pollution vulnerability was found in lodash <4.17.11 where the functions merge, mergeWith, and defaultsDeep
CVE-2018-16487
5.6 - Medium
- February 01, 2019
A prototype pollution vulnerability was found in lodash <4.17.11 where the functions merge, mergeWith, and defaultsDeep can be tricked into adding or modifying properties of Object.prototype.
lodash node module before 4.17.5 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via defaultsDeep, merge, and mergeWith functions, which allows a malicious user to modify the prototype of "Object" via __proto__, causing the addition or modification of an existing property
CVE-2018-3721
6.5 - Medium
- June 07, 2018
lodash node module before 4.17.5 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via defaultsDeep, merge, and mergeWith functions, which allows a malicious user to modify the prototype of "Object" via __proto__, causing the addition or modification of an existing property that will exist on all objects.
Prototype Pollution
