body-parser
Affected
- introduced
2.0.0, fixed2.4.0(semver)
Fixed versions
2.4.0
Fix
- Fixed version
2.4.0npm install [email protected]
Advisory
Also known as: CVE-2026-111181
body-parser vulnerable to Denial of Service via trailing bytes after a compressed request body
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.
High Basis: The source's own band: HIGH
2.0.0, fixed 2.4.0 (semver)2.4.0
2.4.0npm install [email protected]0, fixed 1.20.9 (semver)1.20.9
1.20.9npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0