NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm💎 RubyGems
Not in CISA KEV
MEDIUM severity

CVE-2018-16487 — lodash

MEDIUMFix: lodash/lodash@90e6199

CVE-2018-16487 is a medium-severity (CVSS 5.6) Uncontrolled Resource Consumption 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

Also known asGHSA-4xc9-xhrj-v574
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
1 known
Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs74th percentile — riskier than 74% of all scored CVEsHighest risk
0.01%0.69%1.37%2.05%0.5%1.5%May 26Sep 26Nov 26

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

2 pkgs affected

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.

197Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream
lodashnpm
204.9Mdownloads / week

Description

Versions of lodash before 4.17.11 are vulnerable to prototype pollution.

The vulnerable functions are 'defaultsDeep', 'merge', and 'mergeWith' which allow 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.11 or later.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
📦npmlodashall versions4.17.11npm install lodash@4.17.11
💎RubyGemslodash-railsall versions4.17.11bundle update lodash-rails --conservative

Affected Products

1 product · 1 configurations
Application
lodashlodash
< 4.17.11
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

A prototype pollution vulnerability was found in lodash <4.17.11 where t…

hackerone.comNVDSep 2020

Detection & mitigation playbook

Open-source dependency

  1. Detect

    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.

  2. Fix

    Update lodash to 4.17.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-16487 is resolved across your whole dependency graph.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

Versions of `lodash` before 4.17.11 are vulnerable to prototype pollution. The vulnerable functions are 'defaultsDeep', 'merge', and 'mergeWith' which allow 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.11 or later.
O3 Security · Impact-Aware SCA

Is CVE-2018-16487 in your dependencies?

Find it across npm, RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2018-16487: lodash — Fixed in 4.17.11