CVE-2026-87908

multiparty vulnerable to Denial of Service via unbounded part-header accumulation

Published Sep 11, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
multiparty is a Node.js library for parsing multipart/form-data request bodies. In versions from 2.1.0 up to but not including 4.3.1, the parser does not bound the amount of memory used while accumulating the headers of a single multipart part. An unauthenticated attacker can send a single request whose part carries a very large volume of header bytes, forcing the parser to buffer all of them and exhausting the process memory, which crashes the server. This is a denial of service with no confidentiality or integrity impact. The issue is fixed in multiparty 4.3.1, which caps the size of the accumulated part headers. Users should upgrade to multiparty 4.3.1 or later.

Analysis

AI-generated

Technical impact

The vulnerability arises from an unbounded accumulation of multipart part headers within the multiparty Node.js library. The parser can buffer an arbitrary number of header bytes before processing a request, and a malicious request can cause the library to consume all available memory. The result is that the hosting process crashes, denying service to legitimate users. The weakness is a resource exhaustion flaw, specifically lack of bounds checking during part-header accumulation, classified as CWE‑400, CWE‑770, and CWE‑1050.

Affected Systems

Affected software is the multiparty Node.js library, versions 2.1.0 through 4.3.1 exclusive. Any application that uses these versions to parse multipart/form‑data requests is susceptible. The vulnerability is independent of authentication level; an unauthenticated attacker can trigger it by sending a crafted HTTP request.

Risk and Exploitability

The CVSS score of 7.5 indicates a high risk of service disruption. The EPSS score is 0.00297, indicating a very low probability of exploitation, but the flaw is still actively exploitable in the wild as it requires only a single HTTP request. The vulnerability is not yet listed in the CISA KEV catalog, so it has not been confirmed as a large‑scale exploited vulnerability. The attack vector is likely remote, through a normal HTTP request to a web application that employs the vulnerable multipart parser.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade multiparty to version 4.3.1 or later immediately.
  • Re‑run the application’s functional tests after the upgrade to confirm multipart parsing still behaves as expected.
  • Apply an additional request‑size limit in the web server or reverse proxy to cap multipart header sizes, reducing memory pressure until the library update can be deployed.

Generated by OpenCVE AI on September 24, 2026 at 02:14 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Multiparty
Multiparty multiparty
Vendors & Products Multiparty
Multiparty multiparty
Type Values Removed Values Added
Description multiparty is a Node.js library for parsing multipart/form-data request bodies. In versions from 2.1.0 up to but not including 4.3.1, the parser does not bound the amount of memory used while accumulating the headers of a single multipart part. An unauthenticated attacker can send a single request whose part carries a very large volume of header bytes, forcing the parser to buffer all of them and exhausting the process memory, which crashes the server. This is a denial of service with no confidentiality or integrity impact. The issue is fixed in multiparty 4.3.1, which caps the size of the accumulated part headers. Users should upgrade to multiparty 4.3.1 or later.
Title multiparty vulnerable to Denial of Service via unbounded part-header accumulation
Weaknesses CWE-400
CWE-770
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

Weaknesses
  • CWE-1050

    Excessive Platform Resource Consumption within a Loop

  • CWE-400

    Uncontrolled Resource Consumption

  • CWE-770

    Allocation of Resources Without Limits or Throttling

Sources

Status
PUBLISHED
Assigner
openjs
Published
Updated
Sep 11, 2026, 3:54 PM
Reserved
Sep 9, 2026, 3:07 PM
Status
Awaiting Analysis
Published
Sep 11, 2026, 7:16 AM
Modified
Sep 16, 2026, 7:40 PM
Severity
Important
Public date
Sep 11, 2026, 6:37 AM