CVE-2019-10744 is a critical-severity (CVSS 9.1) CWE-1321 vulnerability in lodash. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for lodash — see the affected versions and patch details below.
Prototype Pollution in lodash
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
lodashnpmlodash-esnpmlodash-amdnpmDescription
Versions of lodash before 4.17.12 are vulnerable to Prototype Pollution. The function defaultsDeep allows a malicious user to modify the prototype of Object via {constructor: {prototype: {...}}} causing the addition or modification of an existing property that will exist on all objects.
Recommendation
Update to version 4.17.12 or later.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | lodash | all versions | 4.17.12npm install lodash@4.17.12 |
| 📦npm | lodash-es | all versions | 4.17.14npm install lodash-es@4.17.14 |
| 📦npm | lodash-amd | all versions | 4.17.13npm install lodash-amd@4.17.13 |
| 📦npm | lodash.defaultsdeep | all versions | 4.6.1npm install lodash.defaultsdeep@4.6.1 |
| 💎RubyGems | lodash-rails | all versions | 4.17.12bundle update lodash-rails --conservative |
Affected Products
big-ip access policy managerf5big-ip advanced firewall managerf5big-ip analyticsf5big-ip application acceleration managerf5big-ip application security managerf5big-ip application visibility and reportingf5Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for lodash, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update lodash to 4.17.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-10744 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
The lodash dependency is included in OpenShift Container Platform (OCP) by Kibana in the aggregated logging stack. Elastic have issued a security advisory (ESA-2019-10) for Kibana for this vulnerability, and in that advisory stated that no exploit vectors had been identified in Kibana. Therefore we rate this issue as…
| Product | Fixed in | Advisory |
|---|---|---|
| Jaeger-1.17 | distributed-tracing/jaeger-all-in-one-rhel7:1.17.2-3 | RHSA-2020:2819 |
| Openshift Service Mesh 1.0 | jaeger-0:v1.13.1.redhat7-1.el7 | RHSA-2020:2362 |
| Red Hat AMQ 7.10.0 | nodejs-lodash | RHSA-2022:5101 |
| Red Hat Fuse 7.10 | nodejs-lodash | RHSA-2021:5134 |
| Red Hat Virtualization Engine 4.3 | ovirt-web-ui-0:1.6.0-1.el7ev | RHSA-2019:3024 |
Frequently Asked Questions
Is CVE-2019-10744 in your dependencies?
Find it across npm, RubyGems, including transitive dependencies.