body-parser vulnerable to Denial of Service via trailing bytes after a compressed request body
High severity
GitHub Reviewed
Published
Oct 22, 2026
in
expressjs/body-parser
•
Updated Oct 23, 2026
Package
Affected versions
>= 2.0.0, < 2.4.0
< 1.20.9
Patched versions
2.4.0
1.20.9
Description
Published by the National Vulnerability Database
Oct 22, 2026
Published to the GitHub Advisory Database
Oct 23, 2026
Reviewed
Oct 23, 2026
Last updated
Oct 23, 2026
Impact
A single request can crash any application using
body-parserwith default options. When a request carries aContent-Encoding(for examplegzip),body-parserpipes 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: falseto 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