Skip to content
Noroxi
NVD / CVE Program· CNA openjs

CVE-2025-13465: Prototype Pollution Vulnerability in Lodash _.unset and _.omit functions

Noroxi assessment

Priority: Monitor (action score 28/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.8% (FIRST EPSS); higher than 78.8% of all records.
  • 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.17.23; Lodash lodash-amd 4.17.23; Lodash lodash-es 4.17.23.

Low priority for now. Upgrade to Lodash lodash 4.17.23; Lodash lodash-amd 4.17.23; Lodash lodash-es 4.17.23 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. An attacker can pass crafted paths which cause Lodash to delete methods from global prototypes. The issue permits deletion of properties but does not allow overwriting their original behavior. The issue is patched from 4.17.23 to 4.18.0 depending on the package: lodash, lodash-es, and lodash-amd in 4.17.23, and the standalone lodash.unset and lodash.omit packages in 4.18.0.

MediumCVSS 6.9 · v4.0—Proof of concept Fix available
Published
Jan 21, 2026
Updated
Oct 15, 2026
EPSS
1.8% · 78th percentile

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
27 / 40 · 6.9 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 1.8%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · openjs
6.9
NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:H/SI:H/SA:H/E:P

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
  • Proof of concept exists, no weaponized module
  • A fix has been released

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

Follow CVE-2025-13465

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.

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

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

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.17.23not affected
    • 4.0.0 and later · before 4.17.23affected · semver
  • Lodash lodash-amd

    • 4.17.23not affected
    • 4.0.0 and later · before 4.17.23affected · semver
  • Lodash lodash-es

    • 4.17.23not affected
    • 4.0.0 and later · before 4.17.23affected · semver
  • Lodash lodash.omit

    • 4.18.0not affected
    • 4.0.0 and later · before 4.18.0affected · semver
  • Lodash lodash.unset

    • 4.18.0not affected
    • 4.0.0 and later · before 4.18.0affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:10cockpit-ha-clusterbefore 0.12.1-1.el10_1.20.12.1-1.el10_1.2
AlmaLinux:10sgx-commonbefore 2.26-7.el102.26-7.el10
AlmaLinux:10sgx-libsbefore 2.26-7.el102.26-7.el10
AlmaLinux:10sgx-mpabefore 2.26-7.el102.26-7.el10
AlmaLinux:10sgx-pccsbefore 2.26-7.el102.26-7.el10
AlmaLinux:10sgx-pccs-adminbefore 2.26-7.el102.26-7.el10
AlmaLinux:10sgx-pckid-toolbefore 2.26-7.el102.26-7.el10
AlmaLinux:10tdx-qgsbefore 2.26-7.el102.26-7.el10
AlmaLinux:9pcsbefore 0.11.10-1.el9_7.20.11.10-1.el9_7.2
AlmaLinux:9pcs-snmpbefore 0.11.10-1.el9_7.20.11.10-1.el9_7.2
AlmaLinux:9sgx-commonbefore 2.26-7.el92.26-7.el9
AlmaLinux:9sgx-libsbefore 2.26-7.el92.26-7.el9
AlmaLinux:9sgx-mpabefore 2.26-7.el92.26-7.el9
AlmaLinux:9sgx-pccsbefore 2.26-7.el92.26-7.el9
AlmaLinux:9sgx-pccs-adminbefore 2.26-7.el92.26-7.el9
AlmaLinux:9sgx-pckid-toolbefore 2.26-7.el92.26-7.el9
AlmaLinux:9tdx-qgsbefore 2.26-7.el92.26-7.el9
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.17.21+dfsg+~cs8.31.198.20210220-104.17.21+dfsg+~cs8.31.198.20210220-10
npmlodashfrom 4.0.0 · before 4.17.234.17.23
npmlodash-amdfrom 4.0.0 · before 4.17.234.17.23
npmlodash-esfrom 4.0.0 · before 4.17.234.17.23
npmlodash.omitfrom 4.0.0 · before 4.18.04.18.0

+96

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
  • Later →CVE-2026-2950Mar 31, 2026 · lodash vulnerable to Prototype Pollution via array path bypass in `_.unset` and `_.omit`
    21Monitor

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.17.23Vendor (CNA)
Lodash lodash-amd4.17.23Vendor (CNA)
Lodash lodash-es4.17.23Vendor (CNA)
Lodash lodash.omit4.18.0Vendor (CNA)
Lodash lodash.unset4.18.0Vendor (CNA)
almalinux:cockpit-ha-cluster0.12.1-1.el10_1.2 · AlmaLinux:10Package registry (OSV)
almalinux:pcs0.11.10-1.el9_7.2 · AlmaLinux:9Package registry (OSV)
almalinux:pcs-snmp0.11.10-1.el9_7.2 · AlmaLinux:9Package registry (OSV)
almalinux:sgx-common2.26-7.el10 · AlmaLinux:10Package registry (OSV)
almalinux:sgx-libs2.26-7.el10 · AlmaLinux:10Package registry (OSV)
almalinux:sgx-mpa2.26-7.el10 · AlmaLinux:10Package registry (OSV)
almalinux:sgx-pccs2.26-7.el10 · AlmaLinux:10Package registry (OSV)
almalinux:sgx-pccs-admin2.26-7.el10 · AlmaLinux:10Package registry (OSV)
almalinux:sgx-pckid-tool2.26-7.el10 · AlmaLinux:10Package registry (OSV)
almalinux:tdx-qgs2.26-7.el10 · AlmaLinux:10Package registry (OSV)
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.17.23Package registry (OSV)
npm:lodash-amd4.17.23Package registry (OSV)
npm:lodash-es4.17.23Package registry (OSV)
npm:lodash.omit4.18.0Package registry (OSV)
npm:lodash.unset4.18.0Package registry (OSV)
opensuse:cockpit-machines346-2.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:cockpit-packages4.1-2.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:dracut-saltboot1.1.0-150000.1.65.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:golang-github-boynux-squid_exporter1.13.0-150000.1.12.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:golang-github-lusitaniae-apache_exporter1.0.10-150000.1.26.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:golang-github-prometheus-alertmanager0.28.1-150100.4.31.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:golang-github-prometheus-node_exporter1.9.1-150100.3.38.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:golang-github-prometheus-prometheus3.5.0-150100.4.29.1 · openSUSE:Leap 15.6Package registry (OSV)

+31

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:02026-03-10

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.

  1. Published
  2. First PoC+47 d
  3. TodayNov 5, 2026+288 d

No history yet (it accumulates with the daily EPSS job).

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.

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-2026-295069 days apartlodash vulnerable to Prototype Pollution via array path bypass in `_.unset` and `_.omit`
    21Monitor

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
Integrity
Availability
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
X

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:H/SI:H/SA:H/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Change log

  1. Fix✗ → ✓

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

References

All records