7.5

CVE-2026-111181: body-parser vulnerable to Denial of Service via trailing bytes after a compressed request body

Awaiting analysis
AliasesDEBIAN-CVE-2026-111181GHSA-27r3-jxmh-p828CGA-4rp7-hfp3-827w
Published 22-10-2026Last modified 22-10-2026

Vulnerability summary

CVE-2026-111181 is a high (CVSS 7.5) Uncaught Exception vulnerability in body-parser. EPSS estimates a 0.39% chance of exploitation in the next 30 days, higher than 32.9% of scored vulnerabilities.

Priority
Prioritisesevere

Severe, CVSS 7.5 (CVE.org); no exploitation reported by the 5 checked sources; EPSS 0% (FIRST, 03-11-2026)

Source freshness unavailable

How is this decided?
CVSS score
7.5/10
010
High · v3.1 (CVE.org)
EPSS score
0.39%
0%100%
Low · Change unavailable
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Timeline

  1. 22-10-2026
    PublishedVulnerability first disclosed.
  2. 22-10-2026
    Last modifiedVulnerability information updated.

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 metrics

7 scores · 7 sources · 1 version

EPSS trend

Probability

0.39%

Chance of exploitation in the next 30 days

Percentile

33%

Versus all other CVEs

30-day change

Change unavailable

Change unavailable

23-10-202603-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Version check

Known conditions: network-reachable, no authentication, no user interaction (CVSS vector). Other conditions: not stated in public data.

Chainguard42 products
  • arangodb-3.11< 3.11.14.6-r3
  • arangodb-3.12All versions (No fix recorded) | < 3.12.12.1-r11
  • argo-workflows-ui-3.7All versions (No fix recorded) | < 3.7.18-r14
  • azuriteAll versions (No fix recorded) | < 3.37.0-r8
  • code-serverAll versions (No fix recorded) | < 4.143.1-r1
Wolfi7 products
  • code-serverAll versions (No fix recorded) | < 4.143.1-r1
  • json-serverAll versions (No fix recorded) | < 0.17.4-r15
  • kubeflow-centraldashboardAll versions (No fix recorded) | < 2.0.0-r7
  • langfuse-3-workerAll versions (No fix recorded) | < 3.225.15-r0 | < 3.225.14-r1
  • thingsboard-tb-js-executorAll versions (No fix recorded) | < 4.4-r7
Body-parser1 product
Debian1 product
  • node-body-parserAll versions (No fix recorded) | < 2.4.0+~1.19.6-1
Npm1 product
  • body-parser≥ 2.0.0, < 2.4.0 | < 1.20.9
Ubuntu1 product
  • node-body-parserAll versions (No fix recorded)

6 vendors · 53 products

References

12 links
Show all 12 references