Is body-parser 2.3.0 vulnerable?

body-parser 2.3.0, a JavaScript package on npm. All 2 versions we track · npm page

1 vulnerability, 1 high

Upgrade body-parser from 2.3.0 to 2.4.0 or later.

Known vulnerabilities in body-parser 2.3.0

  • High CVSS 7.5

    CVE-2026-111181: body-parser vulnerable to Denial of Service via trailing bytes after a compressed request body

    GHSA-27r3-jxmh-p828 · published 23 Oct 2026 · fixed in 2.4.0

How to fix it

With package-lock.json:

npm install body-parser@2.4.0
# if it is an indirect dependency: npm update body-parser (or npm audit fix)
  • If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
  • Check the package's changelog for breaking changes (especially across major versions), update the lockfile with the package manager (never by hand), and run your tests.

Other versions of body-parser

Newest version we track without known advisories: 1.20.9.

VersionKnown vulnerabilitiesHighest severity
2.3.0 (this page) 1 High
1.20.9 0 None

Every version of body-parser →

Licence

body-parser 2.3.0 declares MIT .

Check your whole project

body-parser is one package among hundreds in a lockfile. Upload your lockfile, or paste a public GitHub repository, and get every vulnerable package with the version that fixes it. Free, and no account needed.

Get emailed about new advisories for body-parser (free, no account)

About this data

Vulnerability data: OSV.dev, last checked 22 November 2026. Licence: deps.dev. AIssue checks the versions on this page every day. Severity comes from the advisory's own rating when it has one, else from its CVSS score.