VulnerabilityPublished 31 Mar 2026Updated 28 Oct 2026

CVE-2026-2950: Node lodash · The _.unset and _.omit functions in Lodash are vulnerable to prototype pollution

Affects node-lodashSource GCVE Database

Mentioned vulnerabilities

CVE-2025-13465

Not known to be exploited · CVSS 6.5 Medium · fixed in 2.4.1+dfsg-3ubuntu0.1~esm1 : update node-lodash when convenient.

Data as of 28 Oct 2026, 22:28 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 2.4.1+dfsg-3ubuntu0.1~esm1, 4.17.4+dfsg-1ubuntu0.1~esm1, 4.17.15+dfsg-2ubuntu0.1~esm1 +4

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

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

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 31 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Patches and advisories

ubuntu.com/security/notices/USN-8411-1 (opens in a new tab)

Affected software

Product	Affected	Fixed in
Ubuntu 26.10node-lodash`pkg:deb/ubuntu/node-lodash?arch=source&distro=stonking`Other threats	Affected 4.17.23+dfsg-1 – 4.18.1+dfsg1-2 4 affected builds	Fixed in–
Ubuntu Pro 26.04 LTSnode-lodash`pkg:deb/ubuntu/node-lodash?arch=source&distro=esm-apps/resolute`Other threats	Affected <4.17.23+dfsg-1ubuntu0.1~esm1	Fixed in 4.17.23+dfsg-1ubuntu0.1~esm1
Ubuntu 25.10node-lodash`pkg:deb/ubuntu/node-lodash?arch=source&distro=questing`Other threats	Affected <4.17.21+dfsg+~cs8.31.198.20210220-9ubuntu0.25.10.1	Fixed in 4.17.21+dfsg+~cs8.31.198.20210220-9ubuntu0.25.10.1
Ubuntu Pro 24.04 LTSnode-lodash`pkg:deb/ubuntu/node-lodash?arch=source&distro=esm-apps/noble`Other threats	Affected <4.17.21+dfsg+~cs8.31.198.20210220-9ubuntu0.24.04.1~esm1	Fixed in 4.17.21+dfsg+~cs8.31.198.20210220-9ubuntu0.24.04.1~esm1
Ubuntu Pro 22.04 LTSnode-lodash`pkg:deb/ubuntu/node-lodash?arch=source&distro=esm-apps/jammy`Other threats	Affected <4.17.21+dfsg+~cs8.31.198.20210220-5ubuntu0.1~esm1	Fixed in 4.17.21+dfsg+~cs8.31.198.20210220-5ubuntu0.1~esm1
Ubuntu Pro 20.04 LTSnode-lodash`pkg:deb/ubuntu/node-lodash?arch=source&distro=esm-apps/focal`Other threats	Affected <4.17.15+dfsg-2ubuntu0.1~esm1	Fixed in 4.17.15+dfsg-2ubuntu0.1~esm1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The _.unset and _.omit functions in Lodash are vulnerable to prototype pollution. The fix for CVE-2025-13465 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. The issue is patched from 4.18.0 to 4.18.1 depending on the package: lodash, lodash-es, and lodash-amd in 4.18.1, and the standalone lodash.unset and lodash.omit packages in 4.18.0.

References

Community reviews

Loading reviews…