fix(deps): update dependency body-parser to v1.20.6 [security] - #587
Open
renovate[bot] wants to merge 1 commit into
Open
fix(deps): update dependency body-parser to v1.20.6 [security]#587renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Contributor
Build ReportPlease note:
|
renovate
Bot
force-pushed
the
renovate/npm-body-parser-vulnerability
branch
from
August 26, 2026 12:03
2e548a9 to
ffff608
Compare
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.3→1.20.6Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
body-parser vulnerable to denial of service when invalid limit value silently disables size enforcement
CVE-2026-12590 / GHSA-v422-hmwv-36x6
More information
Details
Impact
When body-parser is configured with an invalid
limitoption value, such as an unparseable string orNaN,bytes.parse()returnsnulland the request body size check is silently skipped. Applications that rely onlimitas their primary safeguard against oversized request bodies will accept arbitrarily large payloads, leading to excessive memory and CPU usage and denial of service.This issue affects applications that pass a programmatically computed or user-configurable value to the
limitoption without validating it first.Patches
This issue is fixed in body-parser@2.3.0 and body-parser@1.20.6 via #698. After the fix, invalid
limitvalues throw a clear error at parser construction time instead of silently disabling enforcement.nullandundefinedcontinue to fall back to the default limit (100kb).Workarounds
Validate
limitbefore passing it to body-parser. For example, parse the value withbytes.parse()at startup and reject any configuration where it returnsnullor a non-finite number.References
Severity
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:LReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
expressjs/body-parser (body-parser)
v1.20.6Compare Source
What's Changed
Full Changelog: expressjs/body-parser@1.20.5...1.20.6
v1.20.5Compare Source
What's Changed
The reason for this release is a fix to the extended urlencoded parser returning objects instead of arrays for large array inputs (> 100) on qs@6.14.2+. (#716)
New Contributors
Special thanks to triager @krzysdz for keeping this on our radar and effectively triaging the specific issue!
Full Changelog: expressjs/body-parser@1.20.4...1.20.5
v1.20.4Compare Source
===================
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.