Skip to content
Noroxi
NVD / CVE Program· CNA openjs

CVE-2026-2950: lodash vulnerable to Prototype Pollution via array path bypass in `_.unset` and `_.omit`

Noroxi assessment

Priority: Monitor (action score 21/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.32% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: lodash lodash 4.18.1; lodash lodash-amd 4.18.1; lodash lodash-es 4.18.1.

Low priority for now. Upgrade to lodash lodash 4.18.1; lodash lodash-amd 4.18.1; lodash lodash-es 4.18.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.3 · v3.1—No exploit Fix available
Published
Mar 31, 2026
Updated
Oct 15, 2026
EPSS
0.3% · 25th percentile

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
21 / 40 · 5.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.3
CNA · openjs
6.5
1.2 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-2950

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for lodash records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
lodashlodash
lodashlodash-amd
lodashlodash-es
lodashlodash.unset

Is the Lodash on your site affected?

The free JavaScript library scanner reads the Lodash version from the files your site loads, matches this record and other known vulnerabilities, and gives the safe version on the same branch. If the version can't be read, it says so. No account needed.

Scan JavaScript libraries

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • lodash lodash4.0.0 and later · before 4.17.23
  • lodash lodash-amd4.0.0 and later · before 4.17.23
  • lodash lodash-es4.0.0 and later · before 4.17.23
  • lodash lodash.unset4.0.0 and later

Versions reported by the vendor

Affected version ranges reported by the assigning authority (openjs). Independent of NVD's CPE analysis and usually ahead of it.

  • lodash lodash

    • 4.18.1not affected
    • 4.17.23 and later · before 4.18.1affected · semver

  • lodash lodash-amd

    • 4.18.1not affected
    • 4.17.23 and later · before 4.18.1affected · semver

  • lodash lodash-es

    • 4.18.1not affected
    • 4.17.23 and later · before 4.18.1affected · semver

  • lodash lodash.omit

    • 4.18.0not affected
    • before 4.18.0affected · semver

  • lodash lodash.unset

    • 4.18.0not affected
    • before 4.18.0affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12node-lodashbefore 4.17.21+dfsg+~cs8.31.198.20210220-9+deb12u14.17.21+dfsg+~cs8.31.198.20210220-9+deb12u1
Debian:13node-lodashbefore 4.17.21+dfsg+~cs8.31.198.20210220-9+deb13u14.17.21+dfsg+~cs8.31.198.20210220-9+deb13u1
Debian:14node-lodashbefore 4.18.1+dfsg-14.18.1+dfsg-1
npmlodashbefore 4.18.04.18.0
npmlodash-amdbefore 4.18.04.18.0
npmlodash-esbefore 4.18.04.18.0
npmlodash.unsetfrom 4.0.0 · before 4.18.04.18.0
Red Hat:enterprise_linux:10.2cockpitbefore 0:356.1-1.el10_20:356.1-1.el10_2
Red Hat:enterprise_linux:10.2cockpit-bridgebefore 0:356.1-1.el10_20:356.1-1.el10_2
Red Hat:enterprise_linux:10.2cockpit-debuginfobefore 0:356.1-1.el10_20:356.1-1.el10_2
Red Hat:enterprise_linux:10.2cockpit-debugsourcebefore 0:356.1-1.el10_20:356.1-1.el10_2
Red Hat:enterprise_linux:10.2cockpit-docbefore 0:356.1-1.el10_20:356.1-1.el10_2
Red Hat:enterprise_linux:10.2cockpit-packagekitbefore 0:356.1-1.el10_20:356.1-1.el10_2
Red Hat:enterprise_linux:10.2cockpit-storagedbefore 0:356.1-1.el10_20:356.1-1.el10_2
Red Hat:enterprise_linux:10.2cockpit-systembefore 0:356.1-1.el10_20:356.1-1.el10_2
Red Hat:enterprise_linux:10.2cockpit-wsbefore 0:356.1-1.el10_20:356.1-1.el10_2
Red Hat:enterprise_linux:10.2cockpit-ws-selinuxbefore 0:356.1-1.el10_20:356.1-1.el10_2
Red Hat:enterprise_linux:9::appstreamcockpit-packagekitbefore 0:356.1-1.el9_80:356.1-1.el9_8
Red Hat:enterprise_linux:9::appstreamcockpit-storagedbefore 0:356.1-1.el9_80:356.1-1.el9_8
Red Hat:enterprise_linux:9::baseoscockpitbefore 0:356.1-1.el9_80:356.1-1.el9_8
Red Hat:enterprise_linux:9::baseoscockpit-bridgebefore 0:356.1-1.el9_80:356.1-1.el9_8
Red Hat:enterprise_linux:9::baseoscockpit-debuginfobefore 0:356.1-1.el9_80:356.1-1.el9_8
Red Hat:enterprise_linux:9::baseoscockpit-debugsourcebefore 0:356.1-1.el9_80:356.1-1.el9_8
Red Hat:enterprise_linux:9::baseoscockpit-docbefore 0:356.1-1.el9_80:356.1-1.el9_8

+20

Same product

lodash: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-4800lodash vulnerable to Code Injection via `_.template` imports key names
    40Plan
  • CVE-2019-10744Versions of lodash lower than 4.17.12 are vulnerable to Prototype Pollution.
    38Monitor
  • CVE-2021-23337Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
    34Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2020-8203Jul 15, 2020 · Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20.
    31Monitor
  • ← EarlierCVE-2020-28500Feb 15, 2021 · Regular Expression Denial of Service (ReDoS)
    23Monitor
  • ← EarlierCVE-2025-13465Jan 21, 2026 · Prototype Pollution Vulnerability in Lodash _.unset and _.omit functions
    28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
lodash lodash4.18.1Vendor (CNA)
lodash lodash-amd4.18.1Vendor (CNA)
lodash lodash-es4.18.1Vendor (CNA)
lodash lodash.omit4.18.0Vendor (CNA)
lodash lodash.unset4.18.0Vendor (CNA)
debian:node-lodash4.17.21+dfsg+~cs8.31.198.20210220-9+deb12u1 · Debian:12Package registry (OSV)
debian:node-lodash4.17.21+dfsg+~cs8.31.198.20210220-9+deb13u1 · Debian:13Package registry (OSV)
npm:lodash4.18.0Package registry (OSV)
npm:lodash-amd4.18.0Package registry (OSV)
npm:lodash-es4.18.0Package registry (OSV)
npm:lodash.unset4.18.0Package registry (OSV)
red hat:cockpit0:356.1-1.el9_8 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:cockpit-bridge0:356.1-1.el9_8 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:cockpit-debuginfo0:356.1-1.el9_8 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:cockpit-debugsource0:356.1-1.el9_8 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:cockpit-doc0:356.1-1.el9_8 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:cockpit-packagekit0:356.1-1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:cockpit-storaged0:356.1-1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:cockpit-system0:356.1-1.el9_8 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:cockpit-ws0:356.1-1.el9_8 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:cockpit-ws-selinux0:356.1-1.el9_8 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:nodejs200:20.20.2-1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs20-bin0:20.20.2-1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs20-devel0:20.20.2-1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs250:25.9.0-1.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs25-bin0:25.9.0-1.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs25-devel0:25.9.0-1.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs25-docs0:25.9.0-1.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs25-full-i18n0:25.9.0-1.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs25-libs0:25.9.0-1.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)

+3

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2025-1346569 days apartPrototype Pollution Vulnerability in Lodash _.unset and _.omit functions
    28Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
low · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
Low
Availability impact
None

Weakness class (CWE)

CWE-1321 · Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (1 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records