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.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - 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. (CVE-2026-111181)

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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. (CVE-2026-111181)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	Name	Product	Family	Type	Severity
477259	SCA: security update for body-parser (GHSA-27r3-jxmh-p828)	Tenable Cloud Security	SCA Checks	Local	high
477259	SCA: security update for body-parser (GHSA-27r3-jxmh-p828)	Tenable Self-Hosted Container Security	SCA Checks	Local	high
371604	Linux Distros Unpatched Vulnerability : CVE-2026-111181	Nessus	Misc.	Local	high

Detections

Analytics

CVE-2026-111181

high

Tenable Plugins

high

high

high