body-parser

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

Upgrading body-parser From 1.17.2 to 1.18.0

Same major only

1 release in betweenevery note read

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

1.17.2yours
1.18.0target

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

Security

3 advisories still affect 1.18.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.18.0
9 Sep 20171 fix
- fixed
  Fix JSON strict violation error to match native parse error

Upgrade to 1.18.0

npm install body-parser@1.18.0

What 1.18.0 needs

Reading 1.18.0's manifest…

Check against your package.json

Which of your other dependencies stand in the way of 1.18.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.18.0.