multer vulnerable to Denial of Service via oversized array index in field names
Published 8 Sept 2026 · Updated 8 Sept 2026
Affected package
- Affected
- <2.3.0
- Fixed in
- 2.3.0
npm install multer@2.3.0Details
Impact
multer is vulnerable to a Denial of Service (DoS) via a crafted array index in multipart field names. The append-field dependency parses bracket notation in field names, and a large numeric index such as items[4294967294] forces allocation of a maximum-length sparse array. A following field with a non-numeric key on the same base then converts that array to an object by iterating its full length, which consumes CPU synchronously and leaves the process unable to handle other requests. A single HTTP request with a crafted multipart body is sufficient to exploit this, and it affects multer 1.x and 2.x.
Patches
Users should upgrade to 2.3.0 and configure limits.fieldArrayIndexLimit to the minimum array index their application requires.
Workarounds
None.
Is GHSA-535w-7cp7-47q4 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected multer, and gives you the command that fixes it.
References
- Linkgithub.com/expressjs/multer/security/advisories/GHSA-535w-7cp7-47q4
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-82333
- Linkgithub.com/expressjs/multer/pull/1438
- Linkgithub.com/expressjs/multer/commit/73c1759fa93b87366bc6dbd7abe1b80ddff7d27c
- Linkcna.openjsf.org/security-advisories.html
- Packagegithub.com/expressjs/multer
- Linkgithub.com/expressjs/multer/releases/tag/v2.3.0
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.