Skip to main content

Lodash EUVDEUVD-2026-17591

| CVE-2026-2950 MEDIUM
Improperly Controlled Modification of Object Prototype Attributes (Prototype Pollution) (CWE-1321)
2026-03-31 openjs GHSA-f23m-r3pf-42rh
5.3
CVSS 3.1 · NVD
View

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V3 - Web Frontend Security Prototype pollution prevention
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Impact

The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U) indicates network-accessible, low-complexity, unauthenticated attack with no user interaction required, making exploitation straightforward. However, CVSS impact metrics show only low integrity (I:L) and low availability (I:L) impact-the attacker can delete prototype properties but cannot overwrite their original behavior, significantly limiting real-world damage compared to full prototype pollution vulnerabilities. The 6.5 score reflects this moderate risk. The vulnerability is a partial bypass of a prior security fix (CVE-2025-13465), suggesting the threat model is known and the attack surface is well-understood by the defender community. Without confirmation of public exploit code (POC) or active exploitation (KEV status not provided), this should be prioritized as a medium-risk remediation task rather than an emergency response, though rapid patching is warranted for widespread JavaScript applications.

Exploit ScenarioDerived

An attacker controlling user input (e.g., via an HTTP request parameter processed by a server-side Lodash utility, or client-side code in a vulnerable web application) could craft a JSON payload with array-wrapped path segments targeting Object.prototype or Number.prototype properties. By passing this payload to _.unset or _.omit, the attacker deletes sensitive prototype properties, potentially disrupting application logic or triggering denial-of-service by breaking core object functionality. For example, deleting Object.prototype.toString could cause cascading failures in template rendering or logging systems. No public exploit code or active exploitation has been identified at time of analysis.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 31, 2026

Prototype pollution in Lodash 4.17.23 and earlier allows unauthenticated remote attackers to delete properties from built-in prototypes (Object.prototype, Number.prototype, String.prototype) via array-wrapped path segments in _.unset and _.omit functions, bypassing the incomplete fix for CVE-2025-13465. The vulnerability has a CVSS score of 6.5 with low integrity and availability impact; no public exploit code or active exploitation has been confirmed at time of analysis.

RemediationAI

Vendor-released patch: Upgrade Lodash to version 4.18.0 or later. This version addresses the incomplete prototype pollution guard by properly validating array-wrapped path segments in _.unset and _.omit functions. No workarounds are available; patching is the only mitigation. For JavaScript projects using npm, package.json should be updated to require lodash@^4.18.0 or lodash-es@^4.18.0 depending on the variant in use. Developers should verify the upgraded version and re-run tests to ensure compatibility with their application code.

Affected VersionsENISA

lodash-es 4.17.23 <4.18.0
lodash.unset 4.0.0 <4.18.0
lodash 4.17.23 <4.18.0
Lodash-amd 4.17.23 <4.18.0

Affected Packages

npm lodash fix: 4.17.23, 4.18.0
npm lodash-amd fix: 4.17.23, 4.18.0
npm lodash-es fix: 4.17.23, 4.18.0
npm lodash.unset fix: 4.18.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 4 packages in npm

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Lodash is a widely-used JavaScript utility library. The vulnerability exists in the prototype pollution guard implemented for _.unset and _.omit functions. The guard checks for string key members but fails to validate array-wrapped path segments, allowing attackers to craft payloads that traverse and delete properties from Object.prototype and other built-in prototypes. This is classified as CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes), a type of prototype pollution attack. The affected CPE strings indicate all variants are vulnerable: lodash (main package), lodash-es (ES module variant), lodash-amd (AMD module variant), and lodash.unset (single-function package).

Know when Lodash gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 5.3 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Red Hat 6.5 MEDIUM

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

Lifecycle Timeline

3
CVSS changed
Jul 24, 2026 - 20:22 NVD
6.5 (MEDIUM) 5.3 (MEDIUM)
Patch released
Apr 02, 2026 - 14:30 nvd
Patch available
CVE Published
Mar 31, 2026 - 19:18 nvd
MEDIUM 6.5

DescriptionNVD

Impact:

Lodash versions 4.17.23 and earlier are vulnerable to prototype pollution in the _.unset and _.omit functions. The fix for (CVE-2025-13465: https://github.com/lodash/lodash/security/advisories/GHSA-xxjr-mmjv-4gpg) 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.

Patches:

This issue is patched in 4.18.0.

Workarounds:

None. Upgrade to the patched version.

Blast Radius

ecosystem impact
† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth
  • 44 npm packages depend on lodash (26 direct, 18 indirect)
  • 1 npm packages depend on lodash-es (1 direct, 0 indirect)

Ecosystem-wide dependent count for version 4.18.0 and other introduced versions.

Threat Intelligence Overview

EPSS Score
0.0%
Top 87% exploitable
Threat Intel
1
1 source
Data Quality
8 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GHSA Vendor GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

Vendor StatusVendor

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy