Skip to main content
VulnerabilityPublished

CVE-2026-113872: multer · Uncaught Exception

Affects multerSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High : upgrade to 2.5.0 soon.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers can reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-10-22.

Patch
Available – fixed in 2.5.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Upgrade multer to 2.5.0.

Affected software

ProductAffectedFixed in
multermulterAffected
  • >=2.0.0 <2.5.0
Fixed in
  • 2.5.0
npmmulterpkg:npm/multerOther threatsAffected
  • >=2.0.0 <2.5.0
Fixed in
  • 2.5.0

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

AI-suggested

Upgrade multer to version 2.5.0 or later where this issue is fixed. As a temporary workaround, use a synchronous fileFilter instead of an asynchronous one to avoid the crash.

Description

A vulnerability in multer versions 2.0.0 through before 2.5.0 allows a Node.js process to crash when using an asynchronous fileFilter. If a request is aborted while the asynchronous fileFilter is pending, an unhandled error event occurs due to a resumed parsing stream without an error listener, causing the process to exit. This issue is fixed in multer 2.5.0.

References

Community reviews

Loading reviews…