body-parser

2.4.0 · 22 Oct 2026MIT201.6M / weekRepository Homepage npm Atom feed

Upgrading body-parser From 1.3.1 to 1.4.0

Same major only

1 release in betweenevery note read

Other targets from 1.3.1Newest 1.x, Clears its 3 advisories1.20.9 Latest2.4.0

1.3.1yours
1.4.0target

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

Before you upgrade

Tick each one off as you go

Deprecate bodyParser() middleware; use .json() and .urlencoded() as needed
deprecated1.4.0
Deprecate urlencoded() without provided extended option
deprecated1.4.0

Security

3 advisories still affect 1.4.0

body-parser vulnerable to Denial of Service via trailing bytes after a compressed request bodyhigh · GHSA-27r3-jxmh-p828
body-parser vulnerable to denial of service when url encoding is enabledhigh · GHSA-qwcr-r2fm-qrc7
body-parser vulnerable to denial of service when invalid limit value silently disables size enforcementlow · GHSA-v422-hmwv-36x6

Upgrading to 1.20.9 clears them.

Release by release

1.4.0
Deprecation19 Jun 20143 new
- deprecated
  Deprecate bodyParser() middleware; use .json() and .urlencoded() as needed
- deprecated
  Deprecate urlencoded() without provided extended option
- new
  Add text parser
- new
  Add raw parser
- new
  Support gzip and deflate bodies

4 other lines we could not sort, mostly version bumps

Check accepted charset in content-type (accepts utf-8)
1.4.0
Check accepted encoding in content-encoding (accepts identity)
1.4.0
lazy-load urlencoded parsers
1.4.0
Parsers split into files for reduced mem usage
1.4.0

1 internal line (docs, tests, tooling) left out.

Upgrade to 1.4.0

npm install body-parser@1.4.0

What 1.4.0 needs

Reading 1.4.0's manifest…

Check against your package.json

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