Is body-parser 2.0 vulnerable?

npm · 3 releases from 2.0.0 to 2.0.2 · latest body-parser is 2.4.0 · checked 1 Nov 2026

Yes: 2 known advisories

Yes. body-parser 2.0.2, the last 2.0 release, is affected by 2 known security advisories (1 high, 1 low), including CVE-2026-111181, CVE-2026-12590. Upgrade to 2.4.0 or later to fix all of them.

Upgrade with:npm install body-parser@2.4.0

Is your project affected?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Advisories affecting body-parser 2.0.2

  • HighCVE-2026-111181GHSA-27r3-jxmh-p82823 Oct 2026

    body-parser vulnerable to Denial of Service via trailing bytes after a compressed request body

    Affected
    >=2.0.0 <2.4.0 · <1.20.9
    Fixed in
    1.20.9, 2.4.0
  • LowCVE-2026-12590GHSA-v422-hmwv-36x620 Jul 2026

    body-parser vulnerable to denial of service when invalid limit value silently disables size enforcement

    Affected
    <1.20.6 · >=2.0.0 <2.3.0
    Fixed in
    1.20.6, 2.3.0

Which of your client projects are still on body-parser 2.0?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact body-parser version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other body-parser versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the npm registry. Refreshed daily.