Vulnerability Database · npm · multiparty · Version
multiparty 3.2.0
3.2.0 is affected by 3 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 4.3.1.
Critical 0 High 3 Medium 0 Low 0 Unrated 0
-
Released 18 Jan 2014
Licence MIT
Also known from other sources 3
Newer releases 42
Database updated 23/Oct/2026
Release and licence data published by the npm registry. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
multiparty 3.2.0 vulnerabilities
3 vulnerabilities cover multiparty 3.2.0. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2026-8159: multiparty Denial of Service Vulnerability via Filename Parsing | 7.5 high | 4.3.0 | 18 May 2026 |
| CVE-2026-8162: multiparty Denial of Service via Uncaught Exception in filename Parameter Parsing | 7.5 high | 4.3.0 | 18 May 2026 |
| CVE-2026-8161: multiparty Denial of Service via Prototype Pollution | 7.5 high | 4.3.0 | 18 May 2026 |
Looking for another version, or everything Vulert holds for multiparty?
Questions
About multiparty 3.2.0
Is multiparty 3.2.0 vulnerable?
Yes. 3 vulnerabilities in the Vulert database cover multiparty 3.2.0: 0 critical, 3 high, 0 medium and 0 low. The upgrade Vulert recommends is 4.3.1, and each entry above names the fixed version to move to.
Which version of multiparty should I use instead of 3.2.0?
4.3.1 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 3.2.0 the latest release of multiparty?
No. 3.2.0 was published 18 Jan 2014, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor multiparty for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the multiparty version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.