CVE-2026-8162: multiparty vulnerable to Denial of Service via Uncaught Exception in filename* parameter parsing

Published May 12, 2026
·
Updated

Impact

multiparty@4.2.3 and lower versions are vulnerable to denial of service via uncaught exception. By sending a multipart/form-data request with a Content-Disposition: filename=utf-8'' header containing a malformed percent-encoding (e.g., %FF, %GG), the parser invokes decodeURI on the value without try/catch. The resulting URIError propagates as an uncaught exception and crashes the process. Any service accepting multipart uploads via multiparty is affected.

Patches

Users should upgrade to multiparty@4.3.0 or higher.

Workarounds

None.

Other sources

multiparty@4.2.3 and lower versions are vulnerable to denial of service via uncaught exception. By sending a multipart/form-data request with a Content-Disposition header whose filename parameter contains a malformed percent-encoding, the parser invokes decodeURI on the value without try/catch. The resulting URIError propagates as an uncaught exception and crashes the process. Impact: any service accepting multipart uploads via multiparty is affected. Workarounds: none. 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

Event History

May 12, 2026
CVE Published
via MITRE·09:05 AM
Data Sourced
via MITRE·09:05 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:16 AM
DescriptionSeverityWeaknessAffected Software
May 18, 2026
Advisory Published
via GitHub·05:35 PM
Data Sourced
via GitHub·05:35 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-8162?

CVE-2026-8162 is classified as a Denial of Service vulnerability.

2

How do I fix CVE-2026-8162?

To fix CVE-2026-8162, update the multiparty package to version 4.2.4 or higher.

3

Which versions of multiparty are affected by CVE-2026-8162?

Multiparty versions 4.2.3 and lower are affected by CVE-2026-8162.

4

What type of attack is associated with CVE-2026-8162?

CVE-2026-8162 is associated with a Denial of Service attack via uncaught exceptions.

5

What component is vulnerable in CVE-2026-8162?

The filename* parameter parsing in multiparty is the vulnerable component in CVE-2026-8162.

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