Skip to content
Log inStart free trial

GHSA-xxjr-mmjv-4gpg CVE-2025-13465

Lodash has Prototype Pollution Vulnerability in `_.unset` and `_.omit` functions

Medium npm
Severity
6.9 / 10
Medium · CVSS 4.0
Exploit chance (EPSS)
1.82%
Chance of exploitation in the next 30 days. Higher than 78.78% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-1321 Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
Fix
Available
3 packages have a fixed version

Description

Impact

Lodash versions 4.0.0 through 4.17.22 are vulnerable to prototype pollution in the _.unset and _.omit functions. An attacker can pass crafted paths which cause Lodash to delete methods from global prototypes.

The issue permits deletion of properties but does not allow overwriting their original behavior.

Patches

This issue is patched on 4.17.23.

Affected versions

npm

PackageVulnerableFixed in
lodash
>= 4.0.0, <= 4.17.22
 No fix yet
lodash
>= 4.0.0, < 4.17.23
4.17.23
lodash-amd
>= 4.0.0, <= 4.17.22
 No fix yet
lodash-amd
>= 4.0.0, < 4.17.23
4.17.23
lodash-es
>= 4.0.0, <= 4.17.22
 No fix yet
lodash-es
>= 4.0.0, < 4.17.23
4.17.23
lodash.unset
>= 4.0.0, <= 4.5.2
 No fix yet
lodash.unset
>= 4.0.0, <= 4.5.2
 No fix yet

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

lodash npm → 4.17.23

npm
npm install lodash@4.17.23
yarn
yarn add lodash@4.17.23
pnpm
pnpm add lodash@4.17.23

lodash-amd npm → 4.17.23

npm
npm install lodash-amd@4.17.23
yarn
yarn add lodash-amd@4.17.23
pnpm
pnpm add lodash-amd@4.17.23

lodash-es npm → 4.17.23

npm
npm install lodash-es@4.17.23
yarn
yarn add lodash-es@4.17.23
pnpm
pnpm add lodash-es@4.17.23

Severity breakdown

CVSS 4.0 6.9

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:H/SI:H/SA:H/E:P

Attack vector
Network
Attack complexity
Low
Attack requirements
None
Privileges required
None
User interaction
None
Confidentiality (vulnerable system)
None
Integrity (vulnerable system)
Low
Availability (vulnerable system)
Low
Confidentiality (subsequent systems)
High
Integrity (subsequent systems)
High
Availability (subsequent systems)
High
Exploit maturity
Proof of concept

CVSS 3.1 6.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

Weakness

CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')

The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.

How to prevent it
  • Implementation: By freezing the object prototype first (for example, Object.freeze(Object.prototype)), modification of the prototype becomes impossible.
  • Architecture and Design: By blocking modifications of attributes that resolve to object prototype, such as proto or prototype, this weakness can be mitigated.
  • Implementation: When handling untrusted objects, validating using a schema can be used.
  • Implementation: By using an object without prototypes (via Object.create(null) ), adding object prototype attributes by accessing the prototype via the special attributes becomes impossible, mitigating this weakness.
  • Implementation: Map can be used instead of objects in most cases. If Map methods are used instead of object attributes, it is not possible to access the object prototype or modify it.

References

Advisories

Fixes and patches

Packages

Other links

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-r5fr-rjxr-66jc
lodash vulnerable to Code Injection via `_.template` imports key names
Critical Also affects lodash
GHSA-f23m-r3pf-42rh
lodash vulnerable to Prototype Pollution via array path bypass in `_.unset` and `_.omit`
Medium Also affects lodash
GHSA-29mw-wpgm-hmr9
Regular Expression Denial of Service (ReDoS) in lodash
Medium Also affects lodash
GHSA-35jh-r3h4-6jhm
Command Injection in lodash
High Also affects lodash
GHSA-p6mc-m468-83gw
Prototype Pollution in lodash
High Also affects lodash
GHSA-x5rq-j2xg-h7qm
Regular Expression Denial of Service (ReDoS) in lodash
Medium Also affects lodash
GHSA-jf85-cpcp-j695
Prototype Pollution in lodash
Critical Also affects lodash
GHSA-4xc9-xhrj-v574
Prototype Pollution in lodash
High Also affects lodash

Credits: UlisesGascon, falsyvalues, jdalton, ljharb, lukas-eu

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor