How severe is CVE-2025-13465?

No CVSS score has been assigned to CVE-2025-13465 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-13465?

CVE-2025-13465 affects the following packages: lodash (npm), lodash-amd (npm), lodash-es (npm), lodash.omit (npm), lodash.unset (npm). Ecosystems affected: npm.

How do I fix CVE-2025-13465?

Update lodash to 4.17.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-13465 is resolved across your whole dependency graph.

How do I detect CVE-2025-13465 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for lodash, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-13465 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2025-13465 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-13465 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-13465?

CVE-2025-13465 has an EPSS (Exploit Prediction Scoring System) score of 1.8%, placing it in the 79th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-13465?

CVE-2025-13465 is classified as CWE-1321 (CWE-1321). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-13465 published, and has it been updated?

CVE-2025-13465 was published on January 21, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2025-13465 — lodash

Fix: lodash/lodash@edadd45

CVE-2025-13465 is a CWE-1321 vulnerability in lodash. A fix is available for lodash — see the affected versions and patch details below.

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

Also known asGHSA-xxjr-mmjv-4gpg

Published

Jan 21, 2026

Updated

Oct 28, 2026

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-13465.

EPSS Exploitation Probability

via FIRST.org ↗

1.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs79th percentile — riskier than 79% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

5 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

197Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

lodashnpm

204.9Mdownloads / week

lodash-amdnpm

9Kdownloads / week

lodash-esnpm

70.5Mdownloads / week

Description

Impact

The _.unset, _.omit, and _.pullAt functions are vulnerable to prototype pollution. 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

The issue is patched from 4.17.23 to 4.18.0 depending on the package: lodash, lodash-es, and lodash-amd in 4.17.23, and the standalone lodash.unset and lodash.omit packages in 4.18.0.

Workarounds

None. Upgrade to the patched version.

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`lodash`	≥ 4.0.0&&< 4.17.23	4.17.23`npm install lodash@4.17.23`
📦npm	`lodash-amd`	≥ 4.0.0&&< 4.17.23	4.17.23`npm install lodash-amd@4.17.23`
📦npm	`lodash-es`	≥ 4.0.0&&< 4.17.23	4.17.23`npm install lodash-es@4.17.23`
📦npm	`lodash.omit`	≥ 4.0.0&&< 4.18.0	4.18.0`npm install lodash.omit@4.18.0`
📦npm	`lodash.unset`	≥ 4.0.0&&< 4.18.0	4.18.0`npm install lodash.unset@4.18.0`

Affected Products

1 product · 1 configurations

Application

lodashlodash

≥ 4.0.0 && < 4.17.23

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for lodash, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update lodash to 4.17.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-13465 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This issue is only exploitable by applications using the _.unset and _.omit functions on an object and allowing user input to determine the path of the property to be removed. This issue only allows the deletion of properties but does not allow overwriting their behavior, limiting the impact to a denial of service.…

Workaround published by Red Hat

To mitigate this issue, implement strict input validation before passing any property paths to the _.unset and _.omit functions to block attempts to access the prototype chain. Ensure that strings like __proto__, constructor and prototype are blocked, for example.

Source: Red Hat security advisory for CVE-2025-13465 (CC BY 4.0)

Product	Fixed in	Advisory
Cryostat 4 on RHEL 9	`cryostat/cryostat-openshift-console-plugin-rhel9:4.1.0-17`	RHSA-2026:1845
HawtIO HawtIO 4.4.0	`io.hawt-project`	RHSA-2026:25089
Red Hat Ansible Automation Platform 2.6 for RHEL 9	`automation-platform-ui-0:2.6.6-1.el9ap`	RHSA-2026:3958
Red Hat Data Grid 8.6.0	`org.infinispan-infinispan-console`	RHSA-2026:4630
Red Hat Enterprise Linux 10	`pcs-0:0.12.1-1.el10_1.2`	RHSA-2026:2438
Red Hat Enterprise Linux 10	`linux-sgx-0:2.26-7.el10`	RHSA-2026:18480
Red Hat Enterprise Linux 10	`cockpit-image-builder-0:94.3-1.el10_2`	RHSA-2026:24331
Red Hat Enterprise Linux 10.0 Extended Update Support	`pcs-0:0.12.0-3.el10_0.4`	RHSA-2026:2818

Frequently Asked Questions

### Impact The `_.unset`, `_.omit`, and `_.pullAt` functions are vulnerable to prototype pollution. 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 The issue is patched from 4.17.23 to 4.18.0 depending on the package: `lodash`, `lodash-es`, and `lodash-amd` in 4.17.23, and the standalone `lodash.unset` and `lodash.omit` packages in 4.18.0. ### Workarounds None. Upgrade to the patched version.

O3 Security · Impact-Aware SCA

Is CVE-2025-13465 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works