CVE-2026-2950

lodash vulnerable to Prototype Pollution via array path bypass in `_.unset` and `_.omit`

MEDIUM
5.3
CVSS Score
Published: March 31, 2026 at 07:18 PM UTC
Updated: October 15, 2026 at 07:18 AM UTC
5 products affected across 1 vendorlodash.omitLodashLodash AMD

Using lodash by lodash?

Get instant alerts when new vulnerabilities affect lodash - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.3
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.0.0 ≤ v < 4.17.234.17.23
Affected range stops below 4.17.23, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 4.18.0 (unaffected)
Vendor states this is fixed in 4.18.1 (unaffected)
4.0.0 ≤ v < 4.17.234.17.23
Affected range stops below 4.17.23, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 4.18.0 (unaffected)
Vendor states this is fixed in 4.18.1 (unaffected)
4.0.0 ≤ v < 4.17.234.17.23
Affected range stops below 4.17.23, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 4.18.0 (unaffected)
Vendor states this is fixed in 4.18.1 (unaffected)
v ≥ 4.0.04.0.0
Vendor states this is fixed in 4.18.0 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
LOW
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-1321

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card