CVE-2020-28500

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 7.3% (94th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 7.3%CVSS: 5.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Lodash versions prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
42
EG Risk 42/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation7% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
7.3%
EPSS %ILE
94th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

February 15, 2021

Last Modified

October 8, 2026

Advisory Details (9)

Auto-updated Oct 8, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: github_pr.
generic🔴 Active Exploitation

Regular Expression Denial of Service (ReDoS) in lodash | CVE-2020-28500 | Snyk

https://snyk.io/vuln/SNYK-JS-LODASH-1018905
generic🔴 Active Exploitation

Regular Expression Denial of Service (ReDoS) in org.webjars.npm:lodash | CVE-2020-28500 | Snyk

https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1074893
generic🔴 Active Exploitation

Regular Expression Denial of Service (ReDoS) in org.webjars.bowergithub.lodash:lodash | CVE-2020-28500 | Snyk

https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWERGITHUBLODASH-1074895
generic🔴 Active Exploitation

Regular Expression Denial of Service (ReDoS) in org.webjars.bower:lodash | CVE-2020-28500 | Snyk

https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWER-1074892
generic🔴 Active Exploitation

Regular Expression Denial of Service (ReDoS) in org.webjars:lodash | CVE-2020-28500 | Snyk

https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARS-1074894
generic🔴 Active Exploitation

Regular Expression Denial of Service (ReDoS) in org.fujion.webjars:lodash | CVE-2020-28500 | Snyk

https://snyk.io/vuln/SNYK-JAVA-ORGFUJIONWEBJARS-1074896
generic

NetApp Product Security

https://security.netapp.com/advisory/ntap-20210312-0006/
github_pr

perf: improve performance of `toNumber`, `trim` and `trimEnd` on large input strings

Upstream fix in progress (PR #5065 · lodash/lodash, state=closed)

https://github.com/lodash/lodash/pull/5065
generic
https://cert-portal.siemens.com/productcert/pdf/ssa-637483.pdf

Vendor Advisories for CVE-2020-28500(4)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntunode-lodash-packages (4.17.15+dfsg-2ubuntu0.1~esm1) @ focal2026-10-08ubuntu
redhatrhmtc/openshift-migration-ui-rhel8:v1.7.4-122022-09-13redhat
redhatcockpit-ovirt-0:0.15.1-2.el8ev2021-09-08redhat
redhatopenshift4/ose-thanos-rhel8:v4.8.0-202106291913.p0.git.c358e96.assembly.stream2021-07-27redhat
redhatdistributed-tracing/jaeger-query-rhel8:1.20.4-182021-06-24redhat
redhatovirt-web-ui-0:1.6.9-1.el8ev2021-06-01redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(9 across 6 ecosystems)
npm(4)
PackageVulnerable rangeFix by version rangeDependents
lodash—
  • 4.0.0 up to 4.17.21: fixed in 4.17.21
—
lodash-es—
  • 4.0.0 up to 4.17.21: fixed in 4.17.21
—
lodash.trim—
  • 4.0.0 through 4.5.1: no fix on record
—
lodash.trimend—
  • 4.0.0 through 4.5.1: no fix on record
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
node-lodash—
  • every version up to 4.17.21+dfsg+~cs8.31.173-1: fixed in 4.17.21+dfsg+~cs8.31.173-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-lodash—
  • every version up to 4.17.21+dfsg+~cs8.31.173-1: fixed in 4.17.21+dfsg+~cs8.31.173-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-lodash—
  • every version up to 4.17.21+dfsg+~cs8.31.173-1: fixed in 4.17.21+dfsg+~cs8.31.173-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-lodash—
  • every version up to 4.17.21+dfsg+~cs8.31.173-1: fixed in 4.17.21+dfsg+~cs8.31.173-1
—
RubyGems(1)
PackageVulnerable rangeFix by version rangeDependents
lodash-rails4.0.0 ... 4.6.1 (20 versions)
  • 4.0.0 up to 4.17.21: fixed in 4.17.21
—

Additional Vendor Advisories

(3)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 160 total refreshes for this CVE.

  1. 2026-10-09 20:04 UTCEPSS rescore
  2. 2026-10-08 22:28 UTCVendor advisory
  3. 2026-10-08 21:34 UTCEG score recompute
  4. 2026-10-08 21:34 UTCVendor advisory
  5. 2026-10-08 16:38 UTCEPSS rescore
  6. 2026-10-07 23:44 UTCEPSS rescore
  7. 2026-10-06 15:13 UTCEPSS rescore
  8. 2026-10-05 17:39 UTCEPSS rescore
  9. 2026-10-04 23:18 UTCEPSS rescore
  10. 2026-10-03 14:22 UTCEPSS rescore
  11. 2026-09-30 15:17 UTCEG score recompute
  12. 2026-09-30 14:59 UTCEPSS rescore
  13. 2026-09-29 15:14 UTCEPSS rescore
  14. 2026-09-27 13:41 UTCEPSS rescore
  15. 2026-09-26 15:54 UTCEPSS rescore
  16. 2026-09-26 15:54 UTCEPSS rescore
  17. 2026-09-26 09:55 UTCOSV refresh
  18. 2026-09-24 14:00 UTCEPSS rescore
  19. 2026-09-22 14:43 UTCEPSS rescore
  20. 2026-09-21 20:28 UTCEPSS rescore
  21. 2026-09-19 15:37 UTCEPSS rescore
  22. 2026-09-18 19:23 UTCEPSS rescore
  23. 2026-09-17 19:22 UTCEPSS rescore
  24. 2026-09-16 14:04 UTCEPSS rescore
  25. 2026-09-15 03:06 UTCEPSS rescore
Show 75 more
  1. 2026-09-13 16:43 UTCEPSS rescore
  2. 2026-09-12 14:57 UTCEPSS rescore
  3. 2026-09-11 09:32 UTCEPSS rescore
  4. 2026-09-08 21:56 UTCEPSS rescore
  5. 2026-09-07 15:57 UTCEPSS rescore
  6. 2026-09-06 22:31 UTCOSV refresh
  7. 2026-09-06 13:44 UTCEPSS rescore
  8. 2026-09-05 15:24 UTCEPSS rescore
  9. 2026-09-04 13:57 UTCEPSS rescore
  10. 2026-09-04 05:03 UTCEPSS rescore
  11. 2026-09-02 14:08 UTCEPSS rescore
  12. 2026-09-01 03:32 UTCEPSS rescore
  13. 2026-08-30 19:14 UTCEPSS rescore
  14. 2026-08-30 01:18 UTCEPSS rescore
  15. 2026-08-27 14:21 UTCEPSS rescore
  16. 2026-08-26 14:42 UTCEPSS rescore
  17. 2026-08-25 13:45 UTCEPSS rescore
  18. 2026-08-21 23:45 UTCEPSS rescore
  19. 2026-08-20 22:52 UTCEPSS rescore
  20. 2026-08-20 08:31 UTCOSV refresh
  21. 2026-08-19 17:00 UTCEPSS rescore
  22. 2026-08-18 13:44 UTCEPSS rescore
  23. 2026-08-17 13:43 UTCEPSS rescore
  24. 2026-08-16 14:52 UTCEPSS rescore
  25. 2026-08-16 02:11 UTCEPSS rescore
  26. 2026-08-15 01:26 UTCEPSS rescore
  27. 2026-08-13 21:57 UTCEPSS rescore
  28. 2026-08-12 13:47 UTCEPSS rescore
  29. 2026-08-09 13:43 UTCEPSS rescore
  30. 2026-08-08 16:33 UTCEPSS rescore
  31. 2026-08-07 16:23 UTCEPSS rescore
  32. 2026-08-06 13:43 UTCEPSS rescore
  33. 2026-08-05 03:40 UTCOSV refresh
  34. 2026-08-04 15:06 UTCEPSS rescore
  35. 2026-08-04 10:34 UTCEPSS rescore
  36. 2026-08-02 02:23 UTCEPSS rescore
  37. 2026-08-01 04:12 UTCEPSS rescore
  38. 2026-07-30 16:25 UTCEPSS rescore
  39. 2026-07-30 01:27 UTCEPSS rescore
  40. 2026-07-28 15:33 UTCEPSS rescore
  41. 2026-07-26 14:51 UTCEPSS rescore
  42. 2026-07-25 14:15 UTCEPSS rescore
  43. 2026-07-24 14:14 UTCEPSS rescore
  44. 2026-07-23 14:15 UTCEPSS rescore
  45. 2026-07-23 14:15 UTCEPSS rescore
  46. 2026-07-23 01:52 UTCEG score recompute
  47. 2026-07-22 22:38 UTCEG score recompute
  48. 2026-07-22 14:05 UTCEPSS rescore
  49. 2026-07-21 15:22 UTCEPSS rescore
  50. 2026-07-21 15:22 UTCEPSS rescore
  51. 2026-07-20 17:04 UTCEPSS rescore
  52. 2026-07-20 17:04 UTCEPSS rescore
  53. 2026-07-19 14:28 UTCEPSS rescore
  54. 2026-07-19 14:28 UTCEPSS rescore
  55. 2026-07-19 02:26 UTCEPSS rescore
  56. 2026-07-19 02:26 UTCEPSS rescore
  57. 2026-07-19 01:59 UTCOSV refresh
  58. 2026-07-16 16:59 UTCEPSS rescore
  59. 2026-07-15 16:55 UTCEPSS rescore
  60. 2026-07-15 16:55 UTCEPSS rescore
  61. 2026-07-15 01:57 UTCEPSS rescore
  62. 2026-07-13 22:27 UTCEPSS rescore
  63. 2026-07-13 22:27 UTCEPSS rescore
  64. 2026-07-12 05:44 UTCEPSS rescore
  65. 2026-07-11 08:25 UTCEPSS rescore
  66. 2026-07-11 08:25 UTCEPSS rescore
  67. 2026-07-09 19:07 UTCEPSS rescore
  68. 2026-07-08 15:12 UTCEPSS rescore
  69. 2026-07-07 13:43 UTCEPSS rescore
  70. 2026-07-06 16:25 UTCEPSS rescore
  71. 2026-07-06 16:25 UTCEPSS rescore
  72. 2026-07-06 02:21 UTCEPSS rescore
  73. 2026-07-06 02:21 UTCEPSS rescore
  74. 2026-07-04 06:29 UTCEPSS rescore
  75. 2026-07-04 06:29 UTCEPSS rescore

Related CVEs(same product + same vendor)

Frequently asked(5)

What is CVE-2020-28500?
CVE-2020-28500 is a medium vulnerability published on February 15, 2021. Lodash versions prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions.
When was CVE-2020-28500 disclosed?
CVE-2020-28500 was first published on February 15, 2021, with the most recent update on October 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-28500 actively exploited?
CVE-2020-28500 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 7.3% probability of exploitation in the next 30 days (94th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2020-28500?
CVE-2020-28500 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2020-28500?
A fix for CVE-2020-28500 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2020-28500 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-28500

Explore →

Is Your Infrastructure Affected by CVE-2020-28500?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs