CVE-2026-8161

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 61% 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, nvd
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%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

[email protected] and lower versions are vulnerable to denial of service via uncaught exception. By sending a multipart/form-data request with a field name that collides with an inherited Object.prototype property such as __proto__, constructor, or toString, the parser invokes .push() on the inherited prototype value rather than an array, throwing a TypeError that propagates as an uncaught exception and crashes the process. Impact: any service accepting multipart uploads via multiparty is affected. Workarounds: none. Upgrade to [email protected] or higher.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
39%
KEV
Not listed

Published

May 12, 2026

Last Modified

May 13, 2026

Advisory Details (2)

Auto-updated May 12, 2026
Patch available. Sources: github.
github Patch Available

multiparty vulnerable to Denial of Service via Prototype Pollution leading to Uncaught Exception · Advisory · pillarjs/multiparty · GitHub

https://github.com/pillarjs/multiparty/security/advisories/GHSA-qxch-whhj-8956
generic

Security Advisories | OpenJS Foundation CVE Numbering Authority

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

Vendor Advisories for CVE-2026-8161(1)

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

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
node-multiparty4.2.2-2 ... 4.3.0-1 (9 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
node-multiparty4.2.3-2 ... 4.3.0-1 (6 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-multiparty4.2.3-3, 4.2.3-4, 4.2.3-5, 4.3.0+~4.2.1-1, 4.3.0-1——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-multiparty4.2.3-3, 4.2.3-4, 4.2.3-54.3.0-1—
npm(1)
PackageVulnerable rangeFixed inDependents
multiparty—4.3.0—

Weakness Classification(2)

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

Data Freshness Timeline

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-8161?
CVE-2026-8161 is a high vulnerability published on May 12, 2026. [email protected] and lower versions are vulnerable to denial of service via uncaught exception. By sending a multipart/form-data request with a field name that collides with an inherited Object.prototype property such as proto, constructor, or toString, the parser invokes .push() on the inherited…
When was CVE-2026-8161 disclosed?
CVE-2026-8161 was first published in the National Vulnerability Database on May 12, 2026, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-8161 actively exploited?
CVE-2026-8161 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 61.2% of all scored CVEs.
What is the CVSS score of CVE-2026-8161?
CVE-2026-8161 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-8161?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-8161, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-8161

Explore →

Is Your Infrastructure Affected by CVE-2026-8161?

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

Start Free Scan →Browse All CVEs