---
id: CVE-2026-111181
title: >-
  body-parser vulnerable to Denial of Service via trailing bytes after a
  compressed request body
summary: >-
  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 …
severity: high
cvss: 7.5
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'
cvssSource: cna
cwe:
  - CWE-248
vendor: body-parser
product: body-parser
affected:
  - body-parser >= 2.0.0 < 2.4.0
  - body-parser < 1.20.9
ssvc:
  exploitation: none
  automatable: 'yes'
  technicalImpact: partial
  timestamp: '2026-10-22T18:26:41.855566Z'
published: '2026-10-22'
updated: '2026-10-22'
sourceUpdated: '2026-10-22T19:00:31.729Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-111181'
references:
  - url: >-
      https://github.com/expressjs/body-parser/security/advisories/GHSA-27r3-jxmh-p828
  - url: 'https://cna.openjsf.org/security-advisories.html'
tags:
  - cve.org
ingestedAt: '2026-10-22T22:00:50.374Z'
---

## Overview

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

- `body-parser >= 2.0.0 < 2.4.0`
- `body-parser < 1.20.9`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.