CVE-2025-13465: Lodash Prototype Pollution Vulnerability in `_.unset` and `_.omit` Functions

lodash Updated 22 Jan 2026

Summary

21/01/2026
Yes i
Moderate
6.5

CVE-2025-13465: Lodash has Prototype Pollution Vulnerability in _.unset and _.omit functions. Affects lodash versions >= 4.0.0, < 4.17.23. Fixed in 4.17.23. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Lodash is a widely-used JavaScript utility library that provides modular methods for common programming tasks, such as manipulating arrays, objects, and strings. It is known for its performance and ease of use, making it a popular choice among developers. However, certain versions of Lodash are vulnerable to prototype pollution, which can lead to severe security implications if exploited.

Vulnerability Detail

The vulnerability in Lodash arises from the _.unset and _.omit functions, which allow an attacker to pass specially crafted paths that can delete properties from global prototypes. This can lead to unexpected behavior in applications that rely on these prototypes, potentially compromising the integrity of the application. While the vulnerability permits deletion of properties, it does not allow for overwriting their original behavior, which still poses a risk to application stability and security.

How To Fix

Latest published version: 4.18.1 as of 22 Oct 2026

npm install lodash@4.18.1

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

4.17.23

This is the first release that contains the fix.

npm install lodash@4.17.23

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If immediate updating is not feasible, consider implementing input validation to sanitize paths passed to the _.unset and _.omit functions, ensuring that they do not contain malicious or unexpected values.

Conclusion

The Lodash prototype pollution vulnerability (CVE-2025-13465) poses a significant risk to applications using affected versions of the library. It is crucial to update to version 4.17.23 or later to ensure the security and stability of your application. Additionally, utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for lodash →

Share this vulnerability

FAQ

Prototype pollution is a security vulnerability that allows an attacker to modify the prototype of a base object, potentially leading to the alteration of properties and methods across all instances of that object.

Lodash versions 4.0.0 through 4.17.22 are affected by this vulnerability.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By simply checking your package-lock.json file, you can identify if your application is affected by this vulnerability.

Failing to address this vulnerability can lead to security breaches, where attackers may exploit the prototype pollution to manipulate application behavior, potentially leading to data loss or unauthorized access.

Yes, implementing input validation to sanitize paths used in the _.unset and _.omit functions can help mitigate the risk until you can update to a patched version.

Related vulnerabilities

Recent vulnerabilities recorded for lodash.

How To Fix

Latest published version: 4.18.1 as of 22 Oct 2026

npm install lodash@4.18.1

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

4.17.23

This is the first release that contains the fix.

npm install lodash@4.17.23

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback