VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

multiparty: vulnerability history, versions and safety

multiparty is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 40 releases, first recorded in May 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded H3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 18 May 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all multiparty vulnerabilities

Vulert verdict on multiparty 4.3.1 i

Updated on 23 Oct 2026

Good news: 4.3.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 3.

Package health score 74/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

What to do: Stay on 4.3.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 4.3.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 4.3.1 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 3 in the last year i
  • Latest disclosure 18 May 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 938 packages i
  • Stars 1,294 i
  • OpenSSF scorecard 4/10 i
  • Last release 1 month ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. 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 Versions

Which versions are affected

Every version Vulert tracks for multiparty, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
4.3.1 10 Sep 2026 none MIT — Details →
4.3.0 11 May 2026 none MIT — Details →
4.2.3 21 Jan 2022 H3 MIT Yes Details →
4.2.2 28 Jul 2020 H3 MIT Yes Details →
4.2.1 13 Aug 2018 H3 MIT Yes Details →
4.2.0 30 Jul 2018 H3 MIT Yes Details →
4.1.4 11 May 2018 H3 MIT Yes Details →
4.1.3 22 Jan 2017 H3 MIT Yes Details →
4.1.2 09 May 2015 H3 MIT Yes Details →
4.1.1 19 Jan 2015 H3 MIT Yes Details →
4.1.0 04 Dec 2014 H3 MIT Yes Details →
4.0.0 15 Oct 2014 H3 MIT Yes Details →
3.3.2 08 Aug 2014 H3 MIT Yes Details →
3.3.1 22 Jul 2014 H3 MIT Yes Details →
3.2.10 03 Jul 2014 H3 MIT Yes Details →
3.3.0 03 Jul 2014 H3 MIT Yes Details →
3.2.9 17 Jun 2014 H3 MIT Yes Details →
3.2.8 01 Jun 2014 H3 MIT Yes Details →
3.2.7 26 May 2014 H3 MIT Yes Details →
3.2.6 14 May 2014 H3 MIT Yes Details →
3.2.5 12 May 2014 H3 MIT Yes Details →
3.2.4 26 Mar 2014 H3 MIT Yes Details →
3.2.3 20 Feb 2014 H3 MIT Yes Details →
3.2.2 29 Jan 2014 H3 MIT Yes Details →
3.2.1 27 Jan 2014 H3 MIT Yes Details →
3.2.0 18 Jan 2014 H3 MIT Yes Details →
3.1.2 13 Jan 2014 H3 MIT Yes Details →
3.1.1 13 Dec 2013 H3 MIT Yes Details →
3.1.0 10 Nov 2013 H3 MIT Yes Details →
3.0.0 25 Oct 2013 H3 MIT Yes Details →
2.2.0 15 Oct 2013 H3 MIT Yes Details →
2.1.9 06 Oct 2013 H3 MIT Yes Details →
2.1.8 26 Aug 2013 H3 MIT Yes Details →
2.1.7 23 May 2013 H3 MIT Yes Details →
2.1.6 30 Apr 2013 H3 MIT Yes Details →
2.1.5 10 Apr 2013 H3 MIT Yes Details →
2.1.4 09 Apr 2013 H3 MIT Yes Details →
2.1.3 09 Apr 2013 H3 MIT Yes Details →
2.1.2 08 Apr 2013 H3 MIT Yes Details →
2.1.1 05 Apr 2013 H3 MIT Yes Details →
2.1.0 04 Apr 2013 H3 MIT Yes Details →
2.0.0 02 Apr 2013 H3 MIT Yes Details →

All 42 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 3 of the 3 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for multiparty

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 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-8161: multiparty Denial of Service via Prototype Pollution 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

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About multiparty

Is multiparty safe to use?

Vulert records 3 vulnerabilities for multiparty in npm: 0 critical, 3 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is multiparty's Vulert package health score?

Vulert scores multiparty 74/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of multiparty affected?

No. 4.3.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of multiparty should I use?

4.3.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does multiparty have?

3 vulnerabilities are recorded for multiparty in the npm ecosystem: 0 critical, 3 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new multiparty vulnerabilities disclosed?

3 vulnerabilities were recorded for multiparty in the last 12 months, and the oldest entry in this database dates to 18 May 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of multiparty are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

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.