CVE-2026-87908 multiparty CVE debrief

Who should care

Node.js developers and administrators using the multiparty library should assess exposure and upgrade to version 4.3.1 or later to prevent denial of service attacks. They should also monitor for large header byte requests and review compensating controls for exposed systems while remediation is scheduled and verified.

Why it matters

CVE-2026-87908 is a denial of service vulnerability in the multiparty Node.js library. An unauthenticated attacker can send a request with a large volume of header bytes, causing the parser to buffer all of them and exhausting the process memory, which crashes the server. This issue is fixed in multiparty 4.3.1. Node.js developers and administrators should assess exposure, upgrade to version 4.3.1 or later, and monitor for large header byte requests to prevent denial of service attacks.

• Denial of service through memory exhaustion
• Potential for performance degradation under large header byte requests
• Need for verification of affected versions and remediation status

Technical summary

The multiparty library for Node.js is vulnerable to a denial of service attack due to unbounded memory usage while accumulating headers of a single multipart part. This issue allows an unauthenticated attacker to send a request with a large volume of header bytes, causing the parser to buffer all of them and exhausting the process memory, which crashes the server. The issue is fixed in multiparty 4.3.1, which caps the size of the accumulated part headers. Node.js developers and administrators should assess exposure and upgrade to version 4.3.1 or later to prevent denial of service attacks.

Defensive priority

Upgrade to multiparty 4.3.1 or later to prevent denial of service

Recommended defensive actions

• Upgrade to multiparty 4.3.1 or later
• Assess exposure in Node.js applications using multiparty
• Monitor for large header byte requests
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Review compensating controls for exposed systems while remediation is scheduled and verified.

Evidence notes

The multiparty library for Node.js does not bound the amount of memory used while accumulating the headers of a single multipart part, allowing an unauthenticated attacker to cause a denial of service by sending a request with a large volume of header bytes. This issue is fixed in multiparty 4.3.1, which caps the size of the accumulated part headers.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.