Skip to main content
VulnerabilityPublished

CVE-2026-88932: multer vulnerable to Denial of Service via orphaned disk writes on aborted uploads

Affects multerSource GCVE Database

0
Compare

Mentioned vulnerabilities

Not known to be exploited · CVSS 5.3 Medium : upgrade to 2.4.0 when convenient.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.4.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade multer to 2.4.0.

Affected software

ProductAffectedFixed in
npmmulterAffected
  • >=2.2.0 <2.4.0
Fixed in
  • 2.4.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in multer version 2.4.0 and later. Users should upgrade to version 2.4.0 or higher to resolve this vulnerability. No workarounds are available.

Description

Multer's diskStorage engine has a vulnerability where aborted multipart uploads can leave orphaned files on disk. This occurs in a brief window before the storage engine assigns the file path, allowing unauthenticated attackers to cause denial of service by exhausting disk space. The issue affects versions from 2.2.0 up to but not including 2.4.0. The vulnerability is a partial regression of a previous fix (CVE-2026-5038). No workarounds are available, but upgrading to version 2.4.0 or higher resolves the issue.

References

Community reviews

Loading reviews…