Advisory

GHSA-27r3-jxmh-p828

Also known as: CVE-2026-111181

Summary

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

Details

Impact

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 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 authentication or matching route is required, since parsing runs before routing.

Patches

Fixed in body-parser 2.4.0 and 1.20.9. Upgrade to one of these versions.

Workarounds

Pass inflate: false to the body-parser middleware if the application does not need to accept compressed request bodies. This rejects encoded requests before any decompression stream is created.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-10-23 20:53 UTC
Modified
2026-10-23 21:00 UTC

Affected packages and fixes

body-parser

npm · All systems

Affected

  • introduced 2.0.0, fixed 2.4.0 (semver)

Fixed versions

2.4.0

Fix

body-parser

npm · All systems

Affected

  • introduced 0, fixed 1.20.9 (semver)

Fixed versions

1.20.9

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences