multer

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

Upgrading multer From 1.3.1 to 1.4.4

Same major only

5 releases in betweenevery note read

Other targets from 1.3.1Clears its 8 advisories2.3.0 Latest2.5.0

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

Security

11 advisories still affect 1.4.4

Multer vulnerable to Denial of Service via memory leaks from unclosed streamshigh · GHSA-44fp-w29j-9vj5
Multer vulnerable to Denial of Service from maliciously crafted requestshigh · GHSA-4pg4-qvpc-4q3h
multer vulnerable to Denial of Service via oversized array index in field nameshigh · GHSA-535w-7cp7-47q4

Upgrading to 2.3.0 clears them.

Release by release

1.4.4
7 Dec 20211 fix
- fixed
  Bugfix: Handle missing field names
1.4.3
9 Aug 20211 fix
- fixed
  Bugfix: Avoid deprecated pseudoRandomBytes function
1.4.1 – 1.4.22 releases, nothing new or fixed in the notes
1.4.0
26 Sep 20181 new
- new
  Make Multer errors inherit from MulterError

1 other line we could not sort, mostly version bumps

Bugfix: Make sure that req.file.buffer always is a Buffer
1.4.1

19 internal lines (docs, tests, tooling) left out.

Upgrade to 1.4.4

npm install multer@1.4.4

What 1.4.4 needs

Reading 1.4.4's manifest…

Check against your package.json

Which of your other dependencies stand in the way of 1.4.4. 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.
11 advisories still affect 1.4.4.