Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

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

70
This week
CRITICAL 9.1REMOTEWATCHLISTUPGRADEMITIGATEMITIGATE

CVE-2019-10744 is a critical-severity flaw (CVSS 9.1) affecting lodash, active iq unified manager, active iq unified manager. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • Critical severity
  • EPSS top 8%: very likely to be exploited
  • Public exploit reference
  • Remotely exploitable, no login, no user action
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score9.1 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance5.0% (top 8%)
CISA exploited listNo
WeaknessCWE-1321
Published2019-07-26
Last modified2026-06-17
Publisher (CNA): Snyk · Vendor: lodash · netapp · redhat

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

lodash lodash UPGRADE
Affected: < 4.17.12
Fixed in: 4.17.12
Safe to downgrade to: no unaffected older release
1. Check installed version
npm ls lodash
2. UPGRADE to 4.17.12
npm install lodash@">=4.17.12"
netapp active iq unified manager MITIGATE
Affected: all versions
Fixed in: no fixed release known
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy active-iq-unified-manager || rpm -q active-iq-unified-manager || active-iq-unified-manager --version
No fixed or unaffected release known
Apply the vendor mitigation from the advisory, disable the affected feature, or restrict network access.
netapp active iq unified manager MITIGATE
Affected: all versions
Fixed in: no fixed release known
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy active-iq-unified-manager || rpm -q active-iq-unified-manager || active-iq-unified-manager --version
No fixed or unaffected release known
Apply the vendor mitigation from the advisory, disable the affected feature, or restrict network access.
netapp active iq unified manager MITIGATE
Affected: all versions
Fixed in: no fixed release known
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy active-iq-unified-manager || rpm -q active-iq-unified-manager || active-iq-unified-manager --version
No fixed or unaffected release known
Apply the vendor mitigation from the advisory, disable the affected feature, or restrict network access.
netapp service level manager MITIGATE
Affected: all versions
Fixed in: no fixed release known
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy service-level-manager || rpm -q service-level-manager || service-level-manager --version
No fixed or unaffected release known
Apply the vendor mitigation from the advisory, disable the affected feature, or restrict network access.
redhat virtualization manager DOWNGRADE
Affected: 4.3
Fixed in: no fixed release known
Safe to downgrade to: a release before 4.3
1. Check installed version
apt-cache policy virtualization-manager || rpm -q virtualization-manager || virtualization-manager --version
2. No fixed release: DOWNGRADE to a release before 4.3 (Debian / Ubuntu)
apt-cache madison virtualization-manager sudo apt install virtualization-manager=<VERSION_BEFORE_4.3> sudo apt-mark hold virtualization-manager
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list virtualization-manager sudo dnf downgrade virtualization-manager-<VERSION_BEFORE_4.3> sudo dnf versionlock add virtualization-manager
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.

Exact fixes by distribution

A distro patch exists: prefer upgrading over downgrading.
npm · lodash · FIXED · 4.17.12 · vulnerable: < 4.17.12 · source
npm install lodash@">=4.17.12" npm ls lodash
npm · lodash-es · FIXED · 4.17.14 · vulnerable: < 4.17.14 · source
npm install lodash-es@">=4.17.14" npm ls lodash-es
npm · lodash-amd · FIXED · 4.17.13 · vulnerable: < 4.17.13 · source
npm install lodash-amd@">=4.17.13" npm ls lodash-amd
npm · lodash.defaultsdeep · FIXED · 4.6.1 · vulnerable: < 4.6.1 · source
npm install lodash.defaultsdeep@">=4.6.1" npm ls lodash.defaultsdeep
RubyGems · lodash-rails · FIXED · 4.17.12 · vulnerable: < 4.17.12 · source
bundle update lodash-rails bundle list | grep lodash-rails
Fedora 46 · nodejs-pnpm12 · FIXED · 12.17.0-1.fc46 · FEDORA-2026-7adfb2bcdd · source
sudo dnf upgrade --advisory=FEDORA-2026-7adfb2bcdd
Fedora ELN · wget2 · FIXED · 2.3.0-3.eln159 · FEDORA-2026-811b4922a5 · source
sudo dnf upgrade --advisory=FEDORA-2026-811b4922a5
Ubuntu 20.04 · node-lodash · NOT AFFECTED
Debian 12 · node-lodash · FIXED · 4.17.15+dfsg-1
sudo apt update && sudo apt install --only-upgrade node-lodash dpkg --compare-versions "$(dpkg-query -W -f='${Version}' node-lodash)" ge "4.17.15+dfsg-1" && echo PATCHED || echo STILL-VULNERABLE
Debian 13 · node-lodash · FIXED · 4.17.15+dfsg-1
sudo apt update && sudo apt install --only-upgrade node-lodash dpkg --compare-versions "$(dpkg-query -W -f='${Version}' node-lodash)" ge "4.17.15+dfsg-1" && echo PATCHED || echo STILL-VULNERABLE

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-10744?

lodash: upgrade to 4.17.12; active iq unified manager: mitigate or apply the listed mitigation; active iq unified manager: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2019-10744 being exploited?

CVE-2019-10744 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-10744 affect?

CVE-2019-10744 affects lodash, active iq unified manager, active iq unified manager. Severity is critical (CVSS 9.1). 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.

How urgent is CVE-2019-10744?

Priority 70/100. Critical severity; EPSS top 8%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action; On your watchlist

Software pages

Lodash vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.