How severe is CVE-2026-2950?

CVE-2026-2950 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2026-2950?

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

How do I fix CVE-2026-2950?

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

How do I detect CVE-2026-2950 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-2026-2950 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-2026-2950 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-2950 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-2026-2950?

CVE-2026-2950 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 27th 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-2026-2950?

CVE-2026-2950 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-2026-2950 published, and has it been updated?

CVE-2026-2950 was published on March 31, 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

MEDIUM severity

CVE-2026-2950 — lodash

MEDIUMFix: lodash/lodash@4f0e376

CVE-2026-2950 is a medium-severity (CVSS 6.5) CWE-1321 vulnerability in lodash. A fix is available for lodash — see the affected versions and patch details below.

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

Also known asGHSA-f23m-r3pf-42rh

Published

Mar 31, 2026

Updated

Oct 28, 2026

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

Exploitation data as of Nov 7, 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-2026-2950.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs27th percentile — riskier than 27% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

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-esnpm

70.5Mdownloads / week

lodash-amdnpm

8Kdownloads / week

Description

Impact

The _.unset, _.omit, and _.pullAt functions 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.

Patches

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.

Workarounds

None. Upgrade to the patched version.

References

CVE-2025-13465 / GHSA-xxjr-mmjv-4gpg (original fix that this bypasses)

Affected Packages

5 total 5 fixed

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

Affected Products

4 products · 4 configurations

Application

lodashlodash

≥ 4.0.0 && < 4.17.23

range

Application

lodash-amdlodash

≥ 4.0.0 && < 4.17.23

range

Application

lodash-eslodash

≥ 4.0.0 && < 4.17.23

range

Application

lodash.unsetlodash

≥ 4.0.0

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.18.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-2950 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 HatModerate

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Source: Red Hat security advisory for CVE-2026-2950 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat Enterprise Linux 10	`cockpit-0:356.1-1.el10_2`	RHBA-2026:21388
Red Hat Enterprise Linux 9	`cockpit-0:356.1-1.el9_8`	RHBA-2026:21387
Red Hat Developer Hub 1.10	`rhdh/rhdh-hub-rhel9:1780930740`	RHSA-2026:24841
Red Hat Hardened Images	`nodejs25-main-11.12.1-1.25.9.0.1.1.hum1`	RHSA-2026:7378
Red Hat Hardened Images	`yarnpkg-main-1.22.22-18.1.hum1`	RHSA-2026:7655
Red Hat Hardened Images	`nodejs20-main-10.8.2-1.20.20.2.1.hum1`	RHSA-2026:9455

Frequently Asked Questions

### Impact The `_.unset`, `_.omit`, and `_.pullAt` functions are vulnerable to prototype pollution. 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 The issue is patched from