Repository navigation
chore(deps): update dependency body-parser to v1.20.9 [security] - #563
Open
deckhouse-BOaTswain wants to merge 1 commit into
Open
deckhouse-BOaTswain wants to merge 1 commit into
deckhouse-BOaTswain wants to merge 1 commit into
Conversation
deckhouse-BOaTswain
requested review from
cherep58,
u-veles-a and
vporoshok
as code owners
October 24, 2026 01:19
deckhouse-BOaTswain
enabled auto-merge (squash)
October 24, 2026 01:19
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.20.6->1.20.9body-parser vulnerable to Denial of Service via trailing bytes after a compressed request body
CVE-2026-111181 / GHSA-27r3-jxmh-p828
More information
Details
Impact
A single request can crash any application using
body-parserwith default options. When a request carries aContent-Encoding(for examplegzip),body-parserpipes 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: falseto 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
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Release Notes
expressjs/body-parser (body-parser)
v1.20.9Compare Source
Important: Security
What's Changed
Full Changelog: expressjs/body-parser@1.20.8...1.20.9
v1.20.8Compare Source
Important
Same code base as 1.20.7. This was created to test the new release process.
What's Changed
Full Changelog: expressjs/body-parser@1.20.7...1.20.8
Configuration
📅 Schedule: Branch creation - "" in timezone Europe/Moscow, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.