CVE-2026-5079

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% of all CVEs by exploit prediction. 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, secondary
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Impact: multer versions 1.0.0 through 2.1.1 and 3.0.0-alpha.1 are vulnerable to a Denial of Service via deeply nested field names in multipart form data. The append-field dependency parses bracket notation in field names with no limit on nesting depth, allowing an attacker to force allocation of deeply nested object structures that consume CPU and memory. A single HTTP request with a crafted multipart body is sufficient to exploit this.

Patches: Users should upgrade to multer 2.2.0 (2.x line) or 3.0.0-alpha.2 (3.x prerelease) and configure the new limits.fieldNestingDepth option to the minimum depth their application requires.

Workarounds: Set limits.fields to a reasonable value to reduce the number of fields an attacker can send per request. This does not fully mitigate the issue but limits the impact.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

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
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
EPSS PROB
0.5%
EPSS %ILE
39th
KEV
Not listed

Published

June 15, 2026

Last Modified

June 16, 2026

Advisory Details (2)

Auto-updated Jun 15, 2026
Patch available. Sources: github.
github Patch Available

multer vulnerable to Denial of Service via deeply nested field names · Advisory · expressjs/multer · GitHub

https://github.com/expressjs/multer/security/advisories/GHSA-72gw-mp4g-v24j
generic

Security Advisories | OpenJS Foundation CVE Numbering Authority

https://cna.openjsf.org/security-advisories.html

Vendor Advisories for CVE-2026-5079(6)

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

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatansible-automation-platform/bootc-automation-portal-rhel9:17889435312026-09-09redhat
redhatansible-automation-platform/automation-portal:17887757482026-09-08redhat
redhatrhdh/rhdh-hub-rhel9:17859728432026-08-10redhat
redhatrhdh/rhdh-hub-rhel9:17854116522026-08-03redhat
redhatrhdh/red-hat-developer-hub-backstage-plugin-orchestrator-backend:17853328252026-07-29redhat

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

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
multer—
  • 1.0.0 up to 2.2.0: fixed in 2.2.0
  • 3.0.0-alpha.1 up to 3.0.0-alpha.2: fixed in 3.0.0-alpha.2
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 25× 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 193 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-5079?
CVE-2026-5079 is a high vulnerability published on June 15, 2026. Impact: multer versions 1.0.0 through 2.1.1 and 3.0.0-alpha.1 are vulnerable to a Denial of Service via deeply nested field names in multipart form data. The append-field dependency parses bracket notation in field names with no limit on nesting depth, allowing an attacker to force allocation of…
When was CVE-2026-5079 disclosed?
CVE-2026-5079 was first published on June 15, 2026, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-5079 actively exploited?
CVE-2026-5079 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-5079?
CVE-2026-5079 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-5079?
A fix for CVE-2026-5079 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-5079 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-2026-5079

Explore →

Is Your Infrastructure Affected by CVE-2026-5079?

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

Book a Demo →Browse All CVEs