CVE-2026-111181

NameCVE-2026-111181
Descriptionbody-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.
SourceCVE (at NVD; CERT, ENISA, LWN, oss-sec, fulldisc, Debian ELTS, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more)
Debian Bugs1151838

Vulnerable and fixed packages

The table below lists information on source packages.

Source PackageReleaseVersionStatus
node-body-parser (PTS)bookworm1.20.1+~1.19.2-1vulnerable
trixie1.20.3+~1.19.5-3vulnerable
forky, sid2.3.0+~1.19.6-1vulnerable

The information below is based on the following data on fixed versions.

PackageTypeReleaseFixed VersionUrgencyOriginDebian Bugs
node-body-parsersource(unstable)(unfixed)1151838

Notes

https://github.com/expressjs/body-parser/security/advisories/GHSA-27r3-jxmh-p828

Search for package or bug name: Reporting problems