Skip to content
Noroxi
NVD / CVE Program· CNA snyk

CVE-2019-10744: Versions of lodash lower than 4.17.12 are vulnerable to Prototype Pollution.

Noroxi assessment

Priority: Monitor (action score 38/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: 5% (FIRST EPSS); higher than 92.2% 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.
  • Fixed version: node-lodash (Debian:12) 4.17.15+dfsg-1; lodash (npm) 4.17.12; lodash-amd (npm) 4.17.13.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to node-lodash (Debian:12) 4.17.15+dfsg-1; lodash (npm) 4.17.12; lodash-amd (npm) 4.17.13 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

Versions of lodash lower than 4.17.12 are vulnerable to Prototype Pollution. The function defaultsDeep could be tricked into adding or modifying properties of Object.prototype using a constructor payload.

CriticalCVSS 9.1 · v3.1—Proof of concept Fix available
Published
Jul 25, 2019
Updated
Jun 16, 2026
EPSS
5.0% · 92th percentile

Report tools

JSON

Action score

38

Monitor

Low priority for now.

CVSS
36 / 40 · 9.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
2 / 30 · 5.0%

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-2019-10744

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
netappactive iq unified manager
netappservice level manager
redhatvirtualization manager
oraclebanking extensibility workbench
f5big-ip access policy manager
f5big-ip advanced firewall manager
f5big-ip analytics
f5big-ip application acceleration manager
f5big-ip application security manager
f5big-ip application visibility and reporting
f5big-ip domain name system

and 9 more

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.

  • f5 big-ip access policy manager15.1.0 and later · before 15.1.0.2
  • f5 big-ip access policy manager12.1.0 and later · before 12.1.5.2
  • f5 big-ip access policy manager13.1.0 and later · before 13.1.3.4
  • f5 big-ip access policy manager14.1.0 and later · before 14.1.2.5
  • f5 big-ip access policy manager15.0.0 and later · before 15.0.1.4
  • f5 big-ip advanced firewall manager12.1.0 and later · before 12.1.5.2
  • f5 big-ip advanced firewall manager15.1.0 and later · before 15.1.0.2
  • f5 big-ip advanced firewall manager15.0.0 and later · before 15.0.1.4
  • f5 big-ip advanced firewall manager14.1.0 and later · before 14.1.2.5
  • f5 big-ip advanced firewall manager13.1.0 and later · before 13.1.3.4
  • f5 big-ip analytics15.0.0 and later · before 15.0.1.3
  • f5 big-ip analytics12.1.0 and later · up to 12.1.5 inclusive
  • f5 big-ip analytics13.1.0 and later · up to 13.1.3 inclusive
  • f5 big-ip analytics14.1.0 and later · up to 14.1.2 inclusive
  • f5 big-ip analytics15.1.0 and later · before 15.1.0.2
  • f5 big-ip application acceleration manager12.1.0 and later · before 12.1.5.2
  • f5 big-ip application acceleration manager15.1.0 and later · before 15.1.0.2
  • f5 big-ip application acceleration manager13.1.0 and later · before 13.1.3.4
  • f5 big-ip application acceleration manager14.1.0 and later · before 14.1.2.5
  • f5 big-ip application acceleration manager15.0.0 and later · before 15.0.1.4

Versions reported by the vendor

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

  • Snyk lodash

    • All versions prior to 4.17.12affected

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12node-lodashbefore 4.17.15+dfsg-14.17.15+dfsg-1
npmlodashbefore 4.17.124.17.12
npmlodash-amdbefore 4.17.134.17.13
npmlodash-esbefore 4.17.144.17.14
npmlodash.defaultsdeepbefore 4.6.14.6.1
Red Hat:rhev_manager:4.3ovirt-web-uibefore 0:1.6.0-1.el7ev0:1.6.0-1.el7ev
Red Hat:service_mesh:1.0::el7jaegerbefore 0:v1.13.1.redhat7-1.el70:v1.13.1.redhat7-1.el7
Red Hat:service_mesh:1.0::el7kialibefore 0:v1.0.11.redhat1-1.el70:v1.0.11.redhat1-1.el7
Red Hat:service_mesh:1.0::el8servicemesh-grafanabefore 0:6.2.2-36.el80:6.2.2-36.el8
Red Hat:service_mesh:1.0::el8servicemesh-grafana-prometheusbefore 0:6.2.2-36.el80:6.2.2-36.el8
RubyGemslodash-railsbefore 4.17.124.17.12

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-2021-23337Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
    34Monitor
  • CVE-2020-8203Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20.
    31Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2018-16487Feb 1, 2019 · A prototype pollution vulnerability was found in lodash <4.17.11 where the functions merge, mergeWith, and defaultsDeep can be tricked into
    22Monitor
  • ← EarlierCVE-2019-1010266Jul 17, 2019 · lodash prior to 4.17.11 is affected by: CWE-400: Uncontrolled Resource Consumption.
    27Monitor
  • Later →CVE-2020-28500Feb 15, 2021 · Regular Expression Denial of Service (ReDoS)
    23Monitor

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
debian:node-lodash4.17.15+dfsg-1 · Debian:12Package registry (OSV)
npm:lodash4.17.12Package registry (OSV)
npm:lodash-amd4.17.13Package registry (OSV)
npm:lodash-es4.17.14Package registry (OSV)
npm:lodash.defaultsdeep4.6.1Package registry (OSV)
red hat:jaeger0:v1.13.1.redhat7-1.el7 · Red Hat:service_mesh:1.0::el7Package registry (OSV)
red hat:kiali0:v1.0.11.redhat1-1.el7 · Red Hat:service_mesh:1.0::el7Package registry (OSV)
red hat:ovirt-web-ui0:1.6.0-1.el7ev · Red Hat:rhev_manager:4.3Package registry (OSV)
red hat:servicemesh-grafana0:6.2.2-36.el8 · Red Hat:service_mesh:1.0::el8Package registry (OSV)
red hat:servicemesh-grafana-prometheus0:6.2.2-36.el8 · Red Hat:service_mesh:1.0::el8Package registry (OSV)
RubyGems:lodash-rails4.17.12Package registry (OSV)

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 ×2

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-05-11
Proof-of-concept repository on GitHubstars:02026-09-28

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+2481 d
  3. TodayOct 30, 2026+2653 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.

Credits

All researchers

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

No credits in the CNA record.

Variant candidates

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

No nightly-computed relations.

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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

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
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
High
Availability impact
High

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:H/A:H

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 (4 more)

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

All records