Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Thu, 22 Oct 2026 17:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Body-parser
Body-parser body-parser |
|
| Vendors & Products |
Body-parser
Body-parser body-parser |
Thu, 22 Oct 2026 14:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | body-parser vulnerable to Denial of Service via trailing bytes after a compressed request body | |
| Weaknesses | CWE-248 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: openjs
Published:
Updated: 2026-10-22T19:00:31.729Z
Reserved: 2026-10-15T17:35:18.184Z
Link: CVE-2026-111181
No data.
Status : Awaiting Analysis
Published: 2026-10-22T15:17:04.763
Modified: 2026-10-22T19:17:35.797
Link: CVE-2026-111181
No data.
OpenCVE Enrichment
Updated: 2026-10-22T17:00:09Z
-
CWE-248
Uncaught Exception