multer

2.5.0 · 22 Oct 2026MIT30.7M / weekRepository Homepage npm Atom feed

Upgrading multer From 1.1.0 to 1.2.0

Same major only

1 release in betweenevery note read

Other targets from 1.1.0Newest 1.x1.4.4 Clears its 8 advisories2.3.0 Latest2.5.0

1.1.0yours
1.2.0target

0
changes to make: 0
advisories fixed: 1
new: 0
fixes

Security

8 advisories still affect 1.2.0

Multer vulnerable to Denial of Service via memory leaks from unclosed streamshigh · GHSA-44fp-w29j-9vj5
multer vulnerable to Denial of Service via oversized array index in field nameshigh · GHSA-535w-7cp7-47q4
Multer Vulnerable to Denial of Service via Uncontrolled Recursionhigh · GHSA-5528-5vmv-3xc2

Upgrading to 2.3.0 clears them.

Release by release

1.2.0
4 Aug 20161 new
- new
  Add .none() for accepting only fields

Upgrade to 1.2.0

npm install multer@1.2.0

What 1.2.0 needs

Reading 1.2.0's manifest…

Check against your package.json

Which of your other dependencies stand in the way of 1.2.0. Read once, not stored.

After upgrading

Run the type checker, the linter and the tests.
Build, and look for new deprecation warnings.
Update peer dependencies the new version asks for.
8 advisories still affect 1.2.0.