Cloudanix VulnDB

CVE-2026-77037

High · 7.5

CVSS

7.5

EPSS

0.5%

Published

Aug 28, 2026

CISA due date

—

Cloudanix analysis

Monitor only SSVC: Track

A flaw in how a popular Node.js file-upload component cleans up after interrupted uploads lets attackers keep sending bad requests until the server runs out of resources and stops working.

Exploitation
Remote Unauthenticated
Attacker needs
None
Complexity
Low
Impact
Denial Of Service
Component
Library
Class
Denial of service
Remediation
Upgrade
Effort
Medium
Patch risk
Low

What it actually does

In multer 2.2.0 disk storage, an aborted or truncated upload leaves the write file descriptor open after the visible file is unlinked, leaking descriptors and retaining disk blocks until process exit.

Why it matters to the business

Services accepting file uploads can exhaust file descriptors and disk resources, leading to denial of service and application downtime; the issue affects any Node.js application using multer disk storage for multipart uploads.

How an attack unfolds

An attacker reaches an upload route that uses multer's disk storage and repeatedly sends aborted or malformed multipart/form-data requests; each request leaks one file descriptor and associated disk blocks until the process can no longer allocate resources.

How to fix it

Upgrade multer to version 2.3.0; the updated disk storage engine closes the destination write stream on abnormal source termination and defers cleanup until the stream has closed.

How to confirm the fix worked

Inspect package.json or installed node_modules for multer version < 2.3.0; after upgrade, reproduce aborted uploads while monitoring open file descriptors to confirm descriptors are released.

Typical attack path

  1. Locate an HTTP endpoint that accepts multipart uploads backed by multer diskStorage
  2. Craft and send a series of truncated or aborted multipart requests
  3. Repeat the requests at sufficient volume to exhaust available file descriptors and disk blocks
  4. Observe service degradation or crash due to resource exhaustion

How to detect it

Monitor Node.js processes for steadily increasing open file descriptors associated with temporary upload paths; inspect application and system logs for repeated partial or aborted multipart POST requests to upload endpoints.

What your security team should do

  • Upgrade all instances of multer to 2.3.0 as the primary remediation
  • Temporarily switch high-risk upload handlers to memoryStorage if disk storage is not required
  • Add monitoring for file-descriptor and disk-block usage on upload-handling processes
  • Review and restrict which routes accept unauthenticated multipart uploads

The record

multer is a middleware for handling multipart/form-data in Node.js. In version 2.2.0, when a disk-backed upload is aborted or truncated before the write stream finishes, multer's disk storage engine removes the visible file but does not close the underlying write file descriptor, leaving a deleted but still open descriptor. A remote attacker able to reach an upload route using the built-in disk storage can send repeated aborted or malformed multipart uploads, each one leaking a file descriptor and retaining disk blocks until the process exits, which can exhaust resources and cause a denial of service. The issue is fixed in multer 2.3.0, which closes the destination write stream on abnormal source termination and defers cleanup until the stream has closed. Upgrade to multer 2.3.0 to remediate.

Affected packages

Ecosystem Package Introduced Fixed

Related vulnerabilities