Skip to main content
← All vulnerabilities
CVE-2026-113872GHSA-Q7QP-RJG7-Q26M

multer vulnerable to Denial of Service via a pending asynchronous fileFilter after request teardown

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 2.5.0
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: yes
  • Technical impact: partial

Summary

The multer middleware for Node.js, used to handle multipart/form-data file uploads, is affected when it is configured with an asynchronous fileFilter. A single aborted upload request in that setup can crash the entire Node.js process, causing a denial of service for the application.

Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.

Read the original description

multer is a middleware for Node.js that handles multipart/form-data file uploads. In versions from 2.0.0 before 2.5.0, when multer is configured with an asynchronous fileFilter, a single request can crash the Node.js process. If the request is aborted while one file's asynchronous fileFilter is still pending, the pending callback later resumes a parsing stream that multer has already torn down, and the underlying parser emits an error on a stream that no longer has an error listener, which Node raises as an unhandled error event so the process exits. Any application using multer with an asynchronous fileFilter is affected regardless of storage engine, while uploads using a synchronous fileFilter are not affected. The issue is fixed in multer 2.5.0, and users should upgrade to 2.5.0 or later. As a workaround, use a synchronous fileFilter.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Affected versions

  • multer multer

    From 2.0.0 · fixed in 2.5.0

  • multernpm

    From 2.0.0 · fixed in 2.5.0

References 2

GitHub · expressjs/multer

cna.openjsf.org