CVE-2026-111181: When Uncaught Stream Errors Escape Routing Controls
CVE-2026-111181 exposes a boundary that many application teams do not map explicitly: request parsing happens before the route handler and often before authentication. A failure in that early phase can terminate the Node.js process even when the eventual route would have rejected the request.
Vulnerability overview
Express and the GitHub Advisory Database identify CVE-2026-111181 as a high-severity denial-of-service flaw in npm body-parser. The CVSS 3.1 score is 7.5, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, and the weakness is CWE-248. GHSA-27r3-jxmh-p828 is the corresponding GitHub advisory.
The affected ranges are before 1.20.9 and versions 2.0.0 through 2.3.0. Fixed versions are 1.20.9 and 2.4.0. The vulnerable path requires a compressed request body and a parser configuration that leaves the decompression stream active after the body has been read.
Mechanism and exploitation conditions
The parser pipes the request into a decompressor and reads the decoded body. On the success path, it calls the next middleware while the request can remain connected to the decoder. The successful read has already detached the error listeners installed by raw-body.
A payload with one valid compressed frame, a zero byte, and extra trailing bytes reaches the decoder after the valid frame is complete. The decoder emits an error that has no listener. The pipe re-emits the error, Node.js declares an uncaught exception, and the worker exits.
The parser may be mounted globally, on a router, or on a specific handler. The advisory warns that no matching route is required when parsing runs before routing. The same ordering issue applies to authentication when the parser is mounted first. An attacker therefore needs network access to the parser endpoint, not a valid application identity.
Impact
The direct security consequence is availability loss. The attacker does not need to reach a business handler or complete an authorization decision. The worker can exit while a response is being prepared or before another request is dispatched.
The published vector records no confidentiality or integrity impact. That is an important scope limit, but an abrupt process exit can still affect adjacent traffic and create retry storms. Repeated failures across a cluster can turn a narrow parser issue into a broad service outage.
Affected products and scope
Applications that use a vulnerable body-parser release are affected. The package can be present in a direct dependency or in the resolved tree of Express or another module. Confirm the version from the deployed artifact and not only from a source manifest.
The route table may make one service look safer than another, but the parser placement is the relevant control. A global parser before auth is exposed to requests that never reach a business route. A parser attached after auth has a narrower path and may be harder to reach, but it still needs a fixed package version.
Exposure context
ZoomEye Search for app="Node.js" returned 5,569,018 matches. The CVE Filter vul.cve="CVE-2026-111181" returned 0. The Exposure therefore uses the larger Search count, but it is a Node.js product fingerprint count and not a confirmed affected count.
The result cannot reveal route order, parser options, or the package version. The zero Filter result is not evidence that all deployments are safe. Use the query as a broad inventory cue and verify the actual Express and body-parser state in each service.
Remediation and mitigations
Upgrade to body-parser 1.20.9 or 2.4.0 and rebuild the deployed artifact. If compressed bodies are not needed, set inflate to false to reject encoded requests before decompression. Review the parser's placement and authentication order, but do not rely on ordering changes as a substitute for a fixed dependency.
Add monitoring for uncaught exceptions, process exits, and restart counts. The reviewed sources reported a public reproduction but no confirmed in-the-wild exploitation. A patched parser and a verified runtime are the durable controls because routing controls cannot safely absorb an exception raised during global body parsing.
References
[3] Repository security advisory
[4] NVD CVE page
[5] 1.20.9 release
[6] v2.4.0 release
Top comments (0)