CVE-2026-111181 PUBLISHED

body-parser vulnerable to Denial of Service via trailing bytes after a compressed request body

Assigner: openjs
Reserved: 15.10.2026 Published: 22.10.2026 Updated: 22.10.2026

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.

Metrics

CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS Score: 7.5

Product Status

Vendor body-parser
Product body-parser
Versions Default: unaffected
  • affected from 2.0.0 to 2.4.0 (excl.)
  • Version 2.4.0 is unaffected
  • affected from 0 to 1.20.9 (excl.)
  • Version 1.20.9 is unaffected

Credits

  • blue2cat reporter
  • UlisesGascon remediation developer
  • bjohansebas remediation developer
  • Phillip9587 remediation reviewer

References

Problem Types

  • CWE-248: Uncaught Exception CWE