body-parser vulnerable to Denial of Service via trailing bytes after a compressed request body
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.
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.
What to do
Upgrade to body-parser 2.4.0, 1.20.9, or later. If upgrading is not immediately possible, pass inflate: false to the body-parser middleware to reject compressed request bodies before a decompression stream is created.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| npm package | body-parser | >= 2.0.0, < 2.4.0, < 1.20.9 | 2.4.0, 1.20.9 |
References
- https://github.com/expressjs/body-parser/security/advisories/GHSA-27r3-jxmh-p828
- https://nvd.nist.gov/vuln/detail/CVE-2026-111181
- https://github.com/expressjs/body-parser/commit/1260c3845f54502a05a87594f09a334786bb34d7
- https://github.com/expressjs/body-parser/commit/f7075eae3a84c3473ab4bf0a777da28db208e916
- https://cna.openjsf.org/security-advisories.html
- https://github.com/expressjs/body-parser
- https://github.com/expressjs/body-parser/releases/tag/1.20.9
- https://github.com/expressjs/body-parser/releases/tag/v2.4.0
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H- Weakness (CWE)
CWE-248- Platform
- npm
- Package
body-parser- Disclosed
- 23.10.2026
- Updated
- 28.10.2026 10:00
Sources and licenses · Edited or translated by DockRay; source rights and applicable licenses are retained.
OSV / GitHub Advisory Database - GHSA-27r3-jxmh-p828 - CC BY 4.0
Vulnerability history: body-parser
All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 4
- First → latest
- 09.2024 10.2026
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- High 2
- Medium 1
- Low 1
Disclosures per year
- 2024: 1
- 2025: 1
- 2026: 2
-
body-parser vulnerable to Denial of Service via trailing bytes after a compressed request body this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.