{"id":"CVE-2026-111181","state":"PUBLISHED","title":"body-parser vulnerable to Denial of Service via trailing bytes after a compressed request body","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.","publishedAt":"2026-10-22T14:29:56.577Z","updatedAt":"2026-10-22T19:00:31.729Z","severity":{"score":7.5,"label":"High","version":"3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","source":"openjs"},"assigner":"openjs","products":["body-parser body-parser"],"affected":[{"vendor":"body-parser","product":"body-parser","packageURL":"pkg:npm/body-parser","defaultStatus":"unaffected","versions":[{"version":"2.0.0","status":"affected","lessThan":"2.4.0","versionType":"semver"},{"version":"2.4.0","status":"unaffected","versionType":"semver"},{"version":"0","status":"affected","lessThan":"1.20.9","versionType":"semver"},{"version":"1.20.9","status":"unaffected","versionType":"semver"}]}],"references":["https://github.com/expressjs/body-parser/security/advisories/GHSA-27r3-jxmh-p828","https://cna.openjsf.org/security-advisories.html"],"weaknesses":["CWE-248"],"ingestedAt":"2026-10-29T20:10:33.477Z","source":{"repository":"CVEProject/cvelistV5","path":"cves/2026/111xxx/CVE-2026-111181.json","commit":"556c9d3a8cd17e218bb8e452ba7cd619a384ff47"},"raw":{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-111181","state":"PUBLISHED","datePublished":"2026-10-22T14:29:56.577Z","dateUpdated":"2026-10-22T19:00:31.729Z","assignerShortName":"openjs","assignerOrgId":"ce714d77-add3-4f53-aff5-83d477b104bb","dateReserved":"2026-10-15T17:35:18.184Z"},"containers":{"cna":{"title":"body-parser vulnerable to Denial of Service via trailing bytes after a compressed request body","descriptions":[{"lang":"en","value":"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."}],"affected":[{"vendor":"body-parser","product":"body-parser","packageURL":"pkg:npm/body-parser","defaultStatus":"unaffected","versions":[{"version":"2.0.0","status":"affected","lessThan":"2.4.0","versionType":"semver"},{"version":"2.4.0","status":"unaffected","versionType":"semver"},{"version":"0","status":"affected","lessThan":"1.20.9","versionType":"semver"},{"version":"1.20.9","status":"unaffected","versionType":"semver"}]}],"references":[{"url":"https://github.com/expressjs/body-parser/security/advisories/GHSA-27r3-jxmh-p828"},{"url":"https://cna.openjsf.org/security-advisories.html"}],"metrics":[{"format":"CVSS","cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","baseScore":7.5,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"GENERAL"}]}],"problemTypes":[{"descriptions":[{"cweId":"CWE-248","lang":"en","description":"CWE-248: Uncaught Exception","type":"CWE"}]}],"providerMetadata":{"shortName":"openjs","orgId":"ce714d77-add3-4f53-aff5-83d477b104bb","dateUpdated":"2026-10-22T14:29:56.577Z"},"credits":[{"lang":"en","type":"reporter","value":"blue2cat"},{"lang":"en","type":"remediation developer","value":"UlisesGascon"},{"lang":"en","type":"remediation developer","value":"bjohansebas"},{"lang":"en","type":"remediation reviewer","value":"Phillip9587"}],"x_generator":{"engine":"cve-kit 1.0.0"}},"adp":[{"title":"CISA ADP Vulnrichment","metrics":[{"other":{"type":"ssvc","content":{"id":"CVE-2026-111181","role":"CISA Coordinator","options":[{"Exploitation":"none"},{"Automatable":"yes"},{"Technical Impact":"partial"}],"version":"2.0.3","timestamp":"2026-10-22T18:26:41.855566Z"}}}],"providerMetadata":{"shortName":"CISA-ADP","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","dateUpdated":"2026-10-22T19:00:31.729Z"}}]}}}