body-parser is body parsing middleware for Node.js and Express. In versions before 1.20.9 and in versions from 2.0.0 before 2.4.0, a single request can crash any application using body-parser with default options. When a request carries a Content-Encoding such as gzip, body-parser pipes it into a decompression stream and, after reading the body, leaves that stream 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 matching route is required because body parsing runs before routing, so any endpoint that parses a body is affected. The issue is fixed in body-parser 2.4.0 and 1.20.9, and users should upgrade to one of those versions or later. As a workaround, disable request-body inflation (set the body-parser inflate option to false) so encoded requests are rejected before any decompression stream is created.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 6
- StatusAwaiting Analysis → PublishedNVD modified 2026-10-22 14:29
- StatusPublished → Awaiting AnalysisNVD modified 2026-10-22 19:17
- StatusAwaiting Analysis → PublishedNVD modified 2026-10-22 14:29
- StatusPublished → Awaiting AnalysisNVD modified 2026-10-22 15:25
- StatusReceived → PublishedNVD modified 2026-10-22 14:29
- First seenCVSS 7.5NVD modified 2026-10-22 15:17
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.