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


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 22 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** AZL-110999, AZL-111059, CLSA-2026-1793097203, CLSA-2026-1793098476, CLSA-2026-1793098695, CLSA-2026-1793098724, CLSA-2026-1793099858, CLSA-2026-1793290284, CLSA-2026-1793290420, CLSA-2026-1793290533, CLSA-2026-1793290669, CLSA-2026-1793290802, CLSA-2026-1793290939, CLSA-2026-1793292439, DEBIAN-CVE-2026-111181, ECHO-4304-b90b-ebd6, GHSA-27r3-jxmh-p828, MINI-7vq5-wvm5-q24g, MINI-ghg7-45mr-3274, MINI-mhm7-cmw8-pv8w, MINI-qmwj-m4v6-j252, MINI-vm72-3vgm-9hqr, MINI-vmm8-jpg3-6g8j, MINI-x4f3-5qvq-wrx6, ROOT-APP-NPM-CVE-2026-111181, UBUNTU-CVE-2026-111181

## What is CVE-2026-111181?

CVE-2026-111181 is a high-severity vulnerability in body-parser, published on 22 Oct 2026. 

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

Weakness: CWE-248 (Uncaught Exception)

## Which versions are affected by CVE-2026-111181?

4 open source packages ship an affected version, including body-parser.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `body-parser` | npm | All versions | 1.20.9 |
| `body-parser` | npm | All versions | 1.20.9 |
| `body-parser` | npm | From 2.0.0 | 2.4.0 |
| `body-parser` | npm | From 2.0.0 | 2.4.0 |

## How do I fix CVE-2026-111181?

Upgrade body-parser to a fixed version for your release line: 1.20.9 or 2.4.0.

## Is CVE-2026-111181 being exploited?

There is no known exploitation of CVE-2026-111181 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-111181 and fix it if it is affected.

What it is: CVE-2026-111181 is a high-severity vulnerability in body-parser, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-111181 in the wild and no public exploit code.

Affected packages and fixed versions:
- body-parser (npm): affected all versions; fixed in 1.20.9
- body-parser (npm): affected all versions; fixed in 1.20.9
- body-parser (npm): affected from 2.0.0; fixed in 2.4.0
- body-parser (npm): affected from 2.0.0; fixed in 2.4.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-111181/ (Markdown: https://insights.sbomify.com/CVE-2026-111181/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-111181
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-111181
- OSV: https://osv.dev/vulnerability/CVE-2026-111181

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-111181/
Summaries are generated and may contain mistakes; the official description above is the record.