CVE-2026-111181: body-parser vulnerable to Denial of Service via trailing bytes after a compressed request body
High CVSS 7.5
- OSV id
- GHSA-27r3-jxmh-p828
- Also known as
- CVE-2026-111181
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| body-parser npm |
>= 2.0.0, < 2.4.0 | 2.4.0 |
| body-parser npm |
< 1.20.9 | 1.20.9 |
Versions we track that it affects: body-parser 2.3.0; body-parser 2.3.0
How to fix it
body-parser (npm)
Upgrade body-parser to 2.4.0 or later.
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 changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.
body-parser (npm)
Upgrade body-parser to 1.20.9 or later.
npm install body-parser@1.20.9
# 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 changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.
Not sure whether your project uses an affected version? Check your lockfile below for free.
Details
Impact
A single request can crash any application using body-parser with default options. When a request carries a Content-Encoding (for example gzip), body-parser pipes it into a decompression stream and, after reading the body, leaves that stream piped with no error listener. A payload of one valid compressed frame followed by trailing bytes decodes and the application responds normally, but the trailing bytes then reach the already-finished decoder, which emits an error that is re-thrown as an uncaught exception and terminates the process. No authentication or matching route is required, since parsing runs before routing.
Patches
Fixed in body-parser 2.4.0 and 1.20.9. Upgrade to one of these versions.
Workarounds
Pass inflate: false to the body-parser middleware if the application does not need to accept compressed request bodies. This rejects encoded requests before any decompression stream is created.
References
- GHSA-27r3-jxmh-p828 on OSV.dev
- Web: https://github.com/expressjs/body-parser/security/advisories/GHSA-27r3-jxmh-p828
- Advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-111181
- Web: https://github.com/expressjs/body-parser/commit/1260c3845f54502a05a87594f09a334786bb34d7
- Web: https://github.com/expressjs/body-parser/commit/f7075eae3a84c3473ab4bf0a777da28db208e916
- Web: https://cna.openjsf.org/security-advisories.html
- Package: https://github.com/expressjs/body-parser
- Web: https://github.com/expressjs/body-parser/releases/tag/1.20.9
- Web: https://github.com/expressjs/body-parser/releases/tag/v2.4.0
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: GitHub Advisory Database via OSV.dev (CC-BY 4.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.