CVE-2019-10744: Prototype Pollution in lodash

lodash Updated 02 Oct 2025

Summary

10/07/2019
Yes i
Critical
9.1

CVE-2019-10744: Prototype Pollution in lodash. Affects lodash versions < 4.17.12. Fixed in 4.17.12. How to fix ↓

Also tracked for

The same CVE-2019-10744 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The lodash package is a popular utility library for JavaScript that provides helpful functions for manipulating and working with arrays, objects, and other data types. It is widely used in various applications and frameworks. However, versions of lodash before 4.17.12 are vulnerable to a Prototype Pollution vulnerability.

Vulnerability Detail

The vulnerability in lodash arises from the defaultsDeep function, which allows an attacker to modify the prototype of the Object via a specially crafted payload. By providing {constructor: {prototype: {...}}}, an attacker can add or modify properties that will exist on all objects. This can lead to various security issues, such as arbitrary code execution, information disclosure, or denial of service.

How To Fix

Latest published version: 4.18.1 as of 22 Oct 2026

npm install lodash@4.18.1

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

4.17.12

This is the first release that contains the fix.

npm install lodash@4.17.12

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is crucial to update to the fixed version of the lodash package.

Conclusion

The Prototype Pollution vulnerability in lodash can have serious security implications. It is crucial to update to the fixed version of the lodash package (4.17.12 or later) to mitigate the risk. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for lodash →

Share this vulnerability

FAQ

Prototype Pollution is a vulnerability that allows an attacker to modify the prototype of an object, leading to unexpected behavior and potential security issues.

The impact of this vulnerability can vary depending on how the affected package is used in an application. It can potentially lead to arbitrary code execution, information disclosure, or denial of service.

No, only versions of lodash before 4.17.12 are vulnerable to this specific Prototype Pollution vulnerability.

Yes, the fix for this vulnerability is to update the lodash package to version 4.17.12 or later.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Simply upload your package-lock.json file and it will provide real-time alerts for open-source vulnerabilities.

Related vulnerabilities

Recent vulnerabilities recorded for lodash.

How To Fix

Latest published version: 4.18.1 as of 22 Oct 2026

npm install lodash@4.18.1

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

4.17.12

This is the first release that contains the fix.

npm install lodash@4.17.12

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

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 →
Help improve this record
Report an issue or send feedback