CVE Intelligence
Medium Injection

CVE-2025-13465 — Prototype Pollution Vulnerability in Lodash _.unset and _.omit functions

The _.unset and _.omit functions in Lodash 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. 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.

Published Jan 21, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: openjs

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 1.9% (30-day exploitation probability)+12
  • Technical severity (medium)+3
  • Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
1.85%
ahead of 79% of scored CVEs · Oct 14, 2026
Affects
Lodash
Lodash and 4 more
CVSS base
5.3
Medium · 5 source(s)
Prioritization reference: 8.2 provisional

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
Yes
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Npm Lodash: fixed in version 4.17.23 — github.com (GitHub Security Advisories)
  • Npm Lodash-es: fixed in version 4.17.23 — github.com (GitHub Security Advisories)
  • Npm Lodash-amd: fixed in version 4.17.23 — github.com (GitHub Security Advisories)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Lodash Lodash, Lodash Lodash-amd, Lodash Lodash-es…).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. Apply the fixed version or the patch documented under Remediation.
  4. Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Lodash Lodash ≥ 4.0.0 and < 4.17.23 Vulnerable NIST National Vulnerability Database
Lodash Lodash ≥ 4.0.0 and < 4.17.23 Vulnerable CVE Program (cve.org) e CISA ADP
Lodash Lodash-amd ≥ 4.0.0 and < 4.17.23 Vulnerable CVE Program (cve.org) e CISA ADP
Lodash Lodash-es ≥ 4.0.0 and < 4.17.23 Vulnerable CVE Program (cve.org) e CISA ADP
Lodash Lodash.omit ≥ 4.0.0 and < 4.18.0 Vulnerable CVE Program (cve.org) e CISA ADP
Lodash Lodash.unset ≥ 4.0.0 and < 4.18.0 Vulnerable CVE Program (cve.org) e CISA ADP
Npm Lodash ≥ 4.0.0 and ≤ 4.17.22 Vulnerable GitHub Security Advisories
Npm Lodash-amd ≥ 4.0.0 and ≤ 4.17.22 Vulnerable GitHub Security Advisories
Npm Lodash-es ≥ 4.0.0 and ≤ 4.17.22 Vulnerable GitHub Security Advisories
Npm Lodash.unset ≥ 4.0.0 and ≤ 4.5.2 Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

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

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
6.9 CVSS 4.0 Medium — — ce714d77-add3-4f53-aff5-83d477b104bb via NIST National Vulnerability Database
6.9 CVSS 4.0 Medium — — openjs via CVE Program (cve.org) e CISA ADP
8.2 CVSS 3.1 High 3.9 4.2 0b0ca135-0b70-47e7-9f44-1890c2a1c46c via NIST National Vulnerability Database
6.5 CVSS 3.1 Medium — — GitHub, Inc. via GitHub Security Advisories
5.3 CVSS 3.1 Medium 3.9 1.4 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N (score shown at the top: nvd@nist.gov)
Sources assign different scores within the same severity band. For prioritization we use 8.2 (0b0ca135-0b70-47e7-9f44-1890c2a1c46c via NIST National Vulnerability Database) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-1321 · Prototype Pollution

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 1.85%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Look for parameters with command/query metacharacters and unexpected child processes of the service.
web/proxy/WAF logsnetwork IDS/IPSapplication logsendpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 15, 2026 · GitHub Security Advisories
  • Affected products added · npm/lodash, npm/lodash.unset, npm/lodash-es, npm/lodash-amd
    Oct 15, 2026 · GitHub Security Advisories
  • Affected products removed · 4
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • Affected products added · lodash/lodash, lodash/lodash-amd, lodash/lodash-es, lodash/lodash.unset, lodash/lodash.omit
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • Affected products added · lodash/lodash, lodash-amd/lodash-amd, lodash-es/lodash-es, lodash.unset/lodash.unset
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • CVSS changed · 5.3
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    Jan 21, 2026 · openjs

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 15, 2026 – Oct 15, 2026
  • 2× Official description updated · Oct 13, 2026 – Oct 15, 2026

References

92 on the record

Elsewhere on this site

Lodash
every CVE for this vendor
Injection
same class
CWE-1321
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-4800 lodash vulnerable to Code Injection via `_.template` imports key names Mar 31, 2026
  • CVE-2026-2950 lodash vulnerable to Prototype Pollution via array path bypass in `_.unset` and `_.omit` Mar 31, 2026
  • CVE-2021-23337 Command Injection Feb 15, 2021
  • CVE-2020-28500 Regular Expression Denial of Service (ReDoS) Feb 15, 2021

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-13465 is "Prototype Pollution Vulnerability in Lodash _.unset and _.omit functions", rated Medium. It affects Lodash (Lodash); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.3 describes technical severity. EPSS 1.85% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.