multiparty up to 4.2.3/4.2.x Content-Disposition Parser exceptional condition

Summaryinfo

A vulnerability marked as problematic has been reported in multiparty up to 4.2.3/4.2.x. Affected by this vulnerability is an unknown functionality of the component Content-Disposition Parser. This manipulation causes exceptional condition. The identification of this vulnerability is CVE-2026-8162. It is possible to initiate the attack remotely. There is no exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic was found in multiparty up to 4.2.3/4.2.x. Affected by this vulnerability is an unknown code of the component Content-Disposition Parser. The manipulation with an unknown input leads to a exceptional condition vulnerability. The CWE definition for the vulnerability is CWE-755. The product does not handle or incorrectly handles an exceptional condition. As an impact it is known to affect availability. The summary by CVE is:

[email protected] 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 [email protected] or higher.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-8162 since 05/08/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 314476 (Linux Distros Unpatched Vulnerability : CVE-2026-8162), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 4.3.0 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at Tenable (314476). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• multiparty

Version

• 4.0
• 4.1
• 4.2
• 4.2.0
• 4.2.1
• 4.2.2
• 4.2.3

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion