lodash node module before 4.17.5 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via defaultsDeep, merge, and mer
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.
- Published
- Jun 6, 2018
- Updated
- Jun 16, 2026
- EPSS
- 2.4% · 83th percentile
- CWE
- CWE-471
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
27
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.4%
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| lodash | lodash | cpe:2.3:a:lodash:lodash |
| netapp | active iq unified manager | cpe:2.3:a:netapp:active_iq_unified_manager |
| netapp | system manager | cpe:2.3:a:netapp:system_manager |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- lodash lodashbefore 4.17.5
- netapp active iq unified managerall versions
- netapp system manager9.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (hackerone). Independent of NVD's CPE analysis and usually ahead of it.
HackerOne lodash node module
- Versions before 4.17.5affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | node-lodash | before 4.17.11+dfsg-1 | 4.17.11+dfsg-1 |
| npm | lodash | before 4.17.5 | 4.17.5 |
| npm | lodash | before 4.17.5 | 4.17.5 |
| RubyGems | lodash-rails | before 4.17.5 | 4.17.5 |
Same product
lodash: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-4800lodash vulnerable to Code Injection via `_.template` imports key names40Plan
- CVE-2019-10744Versions of lodash lower than 4.17.12 are vulnerable to Prototype Pollution.38Monitor
- CVE-2021-23337Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.34Monitor
- CVE-2020-8203Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20.31Monitor
- CVE-2025-13465Prototype Pollution Vulnerability in Lodash _.unset and _.omit functions28Monitor
- CVE-2019-1010266lodash prior to 4.17.11 is affected by: CWE-400: Uncontrolled Resource Consumption.27Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:node-lodash | 4.17.11+dfsg-1 · Debian:12 | Package registry (OSV) |
| npm:lodash | 4.17.5 | Package registry (OSV) |
| RubyGems:lodash-rails | 4.17.5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-471 · Modification of Assumed-Immutable Data (MAID)CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Application API Message Manipulation via Man-in-the-MiddleCAPEC-384Low
- Transaction or Event Tampering via Application API ManipulationCAPEC-385Medium
- Application API Navigation RemappingCAPEC-386Medium
- Navigation Remapping To Propagate Malicious ContentCAPEC-387Medium
- Application API Button HijackingCAPEC-388Medium
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- github.com/lodash/lodash/commit/d8e069cc3410082e44eb18fcf8e7f3d08ebe1d4a
- security.netapp.com/advisory/ntap-20190919-0004/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.