ZDF
Sign inSign up

Vulnerabilities

Security fix · CVE-2026-111181

body-parser is body parsing middleware for Node.js and Express.

Published Oct 22, 2026 · catalog updated Oct 22, 2026 · Red Hat Red Hat Enterprise Linux

Last checked Nov 6, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-111181. EPSS is 0.39%. Act only if a listed version of Red Hat Red Hat Enterprise Linux is installed.

Gaps on this record

  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.39%
Remediation
Advisory link
Affected products
npm body-parser · package npm

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • npm body-parserversion unspecified
  • package npmversion unspecified

How to fix CVE-2026-111181

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-111181. EPSS is 0.39%. Act only if a listed version of Red Hat Red Hat Enterprise Linux is installed.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-248. EPSS 0.39%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 22, 2026 · NIST NVD

    Detected

    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

  2. Oct 22, 2026 · NIST NVD

    Updated

    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

Sources

  • CVE.orgVulnerability recordCVE-2026-111181

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-111181

    30-day exploitation probability 0.39%

    first.org
  • GitLab Advisory DatabasePackage advisoryCVE-2026-111181

    A single request can crash any application using body-parser with default options. When a request carries a Content-Encoding (for example gzip), body-parser pipes it into a decompression stream and, after reading the body, leaves that stream piped with no error listener. A payload of one valid compressed frame followed by trailing bytes decodes and the application responds normally, but the traili

    advisories.gitlab.com
  • NIST NVDVulnerability recordCVE-2026-111181

    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-parse

    nvd.nist.gov
  • Red Hat Security DataVendor advisoryCVE-2026-111181

    body-parser: body-parser: Denial of Service via unhandled decompression stream error

    access.redhat.com
  • Snyk Vulnerability DatabasePackage advisorySNYK-JS-BODYPARSER-21431495

    Uncaught Exception

    security.snyk.io

References

Freshness

Last verified in this catalog Nov 6, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • FIRST EPSSNov 6, 2026
  • GitLab Advisory DatabaseOct 27, 2026
  • Snyk Vulnerability DatabaseOct 25, 2026
  • Red Hat Security DataOct 23, 2026
  • CVE.orgOct 23, 2026
  • NIST NVDOct 22, 2026