CVE-2026-8159: multiparty vulnerable to ReDoS via filename parsing

Published May 12, 2026
·
Updated

Impact

multiparty@4.2.3 and lower versions are vulnerable to denial of service via regular expression backtracking in the Content-Disposition filename parameter parser. A multipart upload with a long header value containing !filename="1 repeated can cause regex matching to take seconds, blocking the event loop. Any service accepting multipart uploads via multiparty is affected.

Patches

Users should upgrade to multiparty@4.3.0 or higher.

Workarounds

None. Limiting upload sizes at the proxy/gateway layer reduces but does not eliminate the attack surface, since a small ~8 KB header is sufficient to trigger the vulnerable backtracking.

Resources

- OWASP: Regular expression Denial of Service (ReDoS)

Other sources

multiparty@4.2.3 and lower versions are vulnerable to denial of service via regular expression backtracking in the Content-Disposition filename parameter parser. A crafted multipart upload with a long header value can cause regex matching to take seconds, blocking the event loop. Impact: any service accepting multipart uploads via multiparty is affected. Workarounds: limiting upload sizes at the proxy or gateway layer reduces but does not eliminate the attack surface, since a small header of around 8 KB is sufficient to trigger the vulnerable backtracking. Upgrade to multiparty@4.3.0 or higher.

MITRE

Affected Software

3 affected componentsFixes available
npm/multiparty<=4.2.3
pillarjs Multiparty Node.js<4.3.0
npm/multiparty<=4.2.3
4.3.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/multiparty to a version that resolves this vulnerability.

    Fixed in 4.3.0
  2. Upgrade

    Upgrade multiparty to a version that resolves this vulnerability.

    Fixed in 4.3.0
  3. Compensating control

    Limit upload sizes at the proxy/gateway layer to reduce the attack surface (does not eliminate it), since a small header of around 8 KB can trigger the vulnerable regex backtracking.

Event History

May 12, 2026
CVE Published
via MITRE·08:35 AM
Data Sourced
via MITRE·08:35 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:16 AM
DescriptionSeverityWeaknessAffected Software
May 18, 2026
Advisory Published
via GitHub·05:40 PM
Data Sourced
via GitHub·05:40 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-8159?

CVE-2026-8159 is classified as a denial of service vulnerability due to regular expression backtracking issues.

2

How do I fix CVE-2026-8159?

To fix CVE-2026-8159, upgrade to multiparty version 4.2.4 or later.

3

What versions of multiparty are affected by CVE-2026-8159?

Multiparty versions up to and including 4.2.3 are affected by CVE-2026-8159.

4

What is the impact of CVE-2026-8159 on applications?

The impact of CVE-2026-8159 can lead to denial of service, causing applications to become unresponsive due to regex processing delays.

5

Is there a known exploit for CVE-2026-8159?

As of now, there is no public information regarding active exploits for CVE-2026-8159.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203