Quick answers
- Is CVE-2026-88932 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-88932 being exploited in the wild.
- How severe is CVE-2026-88932?
- Medium severity, with a CVSS score of 5.3, published 14 September 2026.
- Which products and versions are affected?
- multer (npm) >= 2.2.0, < 2.4.0, SEMVER:introduced=2.2.0,fixed=2.4.0.
- Is there a fix for CVE-2026-88932?
- Yes. multer (npm): upgrade to 2.4.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-88932 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-88932?
- Check whether you run multer (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- multer (npm): upgrade to 2.4.0 or later
npm install multer@2.4.0
Technical details
The vulnerability is an incomplete fix for an earlier flaw: multer's diskStorage only cleans up in-flight uploads that have already been assigned a file path. When an upload is aborted before the storage engine assigns the path—particularly with asynchronous destination or filename functions—the uploaded file is written to disk with no removal mechanism in place, and the application cannot clean it up. An unauthenticated network attacker can exploit this by sending repeated multipart/form-data requests and aborting them to accumulate orphaned files in the upload directory or shared temporary directory until disk space is exhausted. The issue affects multer versions 2.2.0 through 2.3.0 and is resolved in version 2.4.0.
Affected products
- Express.js multer 2.2.0 through 2.3.0
Identifiers
- CVE-2026-88932
- GHSA-3pph-fpjx-jg34
Timeline
- 2026-09-14: disclosed: CVE-2026-88932 published
- 2026-09-14: patched: Fixed in multer 2.4.0