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 C…
Historical advisory saved 1 Nov 2026 02:12:09 UTC. The publisher may have updated it since then. Latest advisory.
euvd · EUVD-2026-108189
Publishedbody-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.
Additional publisher context
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Oct 22, 2026, 2:29:56 PM
dateUpdated: Oct 22, 2026, 7:00:31 PM
5 related source bulletins · separate from aliases
msrc_CVE-2026-111181: body-parser vulnerable to Denial of Service via trailing bytes after a compressed request body
CVE-2026-111181
RHSA-2026:90388: Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update
CVE-2026-65627 · CVE-2026-100352 · CVE-2026-100353 · CVE-2026-100354 · CVE-2026-110095 · CVE-2026-110180 · CVE-2026-110306 · CVE-2026-110725 · CVE-2026-110816 · CVE-2026-111181
RHSA-2026:90990: Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update
CVE-2026-79656 · CVE-2026-110095 · CVE-2026-110180 · CVE-2026-110306 · CVE-2026-110725 · CVE-2026-111181
RHSA-2026:91181: Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update
CVE-2026-79656 · CVE-2026-103506 · CVE-2026-110095 · CVE-2026-110180 · CVE-2026-110306 · CVE-2026-110725 · CVE-2026-111181
RHSA-2026:91292: Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update
CVE-2026-79656 · CVE-2026-100352 · CVE-2026-100353 · CVE-2026-100354 · CVE-2026-103506 · CVE-2026-110095 · CVE-2026-110180 · CVE-2026-110306 · CVE-2026-110725 · CVE-2026-111181
- Source published
- Oct 22, 2026, 2:29:56 PM (timezone not stated)
- Source modified
- Oct 22, 2026, 7:00:31 PM (timezone not stated)
- Saved here
- 1 Nov 2026 02:12:09 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
EUVD CVSS 3.1 · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H