Vulnerability 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.
CVSS Score
HIGH
Related Weaknesses (CWE)
References
- https://cna.openjsf.org/security-advisories.html
- https://github.com/expressjs/body-parser/security/advisories/GHSA-27r3-jxmh-p828
FAQ
What is CVE-2026-111181?
CVE-2026-111181 is a vulnerability with a CVSS score of 7.5 (HIGH). 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 def...
How severe is CVE-2026-111181?
CVE-2026-111181 has been rated HIGH with a CVSS base score of 7.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-111181?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.