PoC Monitor
← All CVEs
CVE-2026-111181published 22 Oct 2026 14:29 UTCData: JSON · API

Body-parser

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

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.5high · scored by CNA · CWE-248
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

body-parser body-parser
  • >= 2.0.0, < 2.4.0
  • < 1.20.9

Fixed in 2.4.0, 1.20.9

Mitigation

Upgrade body-parser to 2.4.0 or 1.20.9 or later.

References

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published22 Oct 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.