Answer in brief
CVE-2026-2950 records a Medium severity (CVSS 6.5) vulnerability in lodash vulnerable to Prototype Pollution via array path bypass in `_.unset` and `_.omit`. The current sources do not mark it as known exploited. The current feed maps lodash/lodash (generic), lodash/lodash-amd (generic), lodash/lodash-es (generic), lodash/lodash.omit (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps lodash/lodash (generic), lodash/lodash-amd (generic), lodash/lodash-es (generic), lodash/lodash.omit (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| lodash/lodashgeneric | >=4.17.23 <4.18.1 | 4.18.1 |
| lodash/lodash-amdgeneric | >=4.17.23 <4.18.1 | 4.18.1 |
| lodash/lodash-esgeneric | >=4.17.23 <4.18.1 | 4.18.1 |
| lodash/lodash.omitgeneric | >=0 <4.18.0 | 4.18.0 |
| lodash/lodash.unsetgeneric | >=0 <4.18.0 | 4.18.0 |
Published upstream
Mar 31, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.