CVE-2026-111181

High

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.

SeverityHigh
CVSS7.5
Exploit probability—
ProductBody-parser
PublishedOct 22, 2026
First seenOct 22, 2026
Weakness typeCWE-248CWE-248

How to fix

Update
  • body-parser2.4.0, 1.20.9 or later

Affected products

ProductAffected versionsFixed in
body-parsernpm2.0.0 ≤ v < 2.4.0, v < 1.20.92.4.0, 1.20.9

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.