lodash vulnerable to Prototype Pollution via array path bypass in `_.unset` and `_.omit`
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.18.1, 4.18.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
The .unset and .omit functions in Lodash are vulnerable to prototype pollution. The fix for CVE-2025-13465 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. The issue is patched from 4.18.0 to 4.18.1 depending on the package: lodash, lodash-es, and lodash-amd in 4.18.1, and the standalone lodash.unset and lodash.omit packages in 4.18.0.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- lodash lodash
From 4.17.23 · fixed in 4.18.1
- lodash lodash-es
From 4.17.23 · fixed in 4.18.1
- lodash lodash-amd
From 4.17.23 · fixed in 4.18.1
- lodash lodash.unset
fixed in 4.18.0
- lodash lodash.omit
fixed in 4.18.0
- lodashnpm
fixed in 4.18.0
- lodash-esnpm
fixed in 4.18.0
- lodash-amdnpm
fixed in 4.18.0
- lodash.unsetnpm
From 4.0.0 · fixed in 4.18.0