Skip to content
Fencer Vulns
high 7.5

CVE-2026-111181 json

body-parser vulnerable to Denial of Service via trailing bytes after a compressed request body

published 2026-10-22 18 d ago modified 2026-10-23 16 d ago also EUVD-2026-108189 , GHSA-27r3-jxmh-p828

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 33%
public exploits
0
none known

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

Patch / fix

  • npm body-parser 1.20.9, 2.4.0
  • body-parser body-parser 1.20.9, 2.4.0
  • node-body-parser Debian 14 2.4.0+~1.19.6-1

debian advisories DEBIAN-CVE-2026-111181

  • agama-web-ui openSUSE Tumbleweed 25+475.275dd4727-56.1
  • git-bug openSUSE Tumbleweed 0.11.0-4.1

opensuse advisories openSUSE-SU-2026:12424-1openSUSE-SU-2026:12429-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-111181 updated cvss 7.5

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

  • Red Hat Hardened Images grafana13.1 13.1.8-0.5.hum1, grafana13.2 13.2.4-0.4.hum1, grafana12.4 12.4.13-0.4.hum1, grafana12.4 12.4.13-0.5.hum1
    fixed: vendor fix RHSA-2026:90388
  • Red Hat Hardened Images prometheus3.13 3.13.4-0.2.hum1
    not affected: component not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
17 d ago

Exploit prediction

0.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
npm body-parser
>=2.0.0, <2.4.0
<1.20.9
2.4.0
1.20.9

Affected products

  • body-parser body-parser

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.