lodash vulnerable to Prototype Pollution via array path bypass in `_.unset` and `_.omit`
lodash · lodash-es · lodash-amd · lodash.unset
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| lodash npm |
|
|
| lodash-es npm |
|
|
| lodash-amd npm |
lodash · lodash-es · lodash-amd · lodash.unset
| Product | Affected | Fixed in |
|---|---|---|
| lodash npm |
|
|
| lodash-es npm |
|
|
| lodash-amd npm |
≥ 4.17.23 · < 4.18.1
|
| lodash.unset npm |
|
|
| lodash.omit npm |
|
|
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.
From the CVE record · openjs
The _.unset and _.omit functions are vulnerable to prototype pollution when passed attacker-controlled, array-wrapped path segments. An attacker can delete properties from built-in prototypes but cannot overwrite their original behavior. The input does not specify whether exploitation requires network access, authentication, or user interaction.
Check npm installations of lodash, lodash-es, or lodash-amd at versions >=4.17.23 <4.18.1, and lodash.unset or lodash.omit at versions <4.18.0.