fix(deps): update dependency body-parser to v1.20.6 [security]#91
Open
renovate[bot] wants to merge 1 commit into
Open
fix(deps): update dependency body-parser to v1.20.6 [security]#91renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/npm-body-parser-vulnerability
branch
from
August 10, 2025 14:09
f2c268e to
be3dd00
Compare
renovate
Bot
force-pushed
the
renovate/npm-body-parser-vulnerability
branch
from
August 19, 2025 18:07
be3dd00 to
275ec13
Compare
renovate
Bot
force-pushed
the
renovate/npm-body-parser-vulnerability
branch
from
November 25, 2025 16:35
275ec13 to
687a64b
Compare
renovate
Bot
force-pushed
the
renovate/npm-body-parser-vulnerability
branch
from
November 25, 2025 21:59
687a64b to
e10b6f9
Compare
renovate
Bot
force-pushed
the
renovate/npm-body-parser-vulnerability
branch
2 times, most recently
from
March 30, 2026 20:51
e10b6f9 to
a270256
Compare
renovate
Bot
force-pushed
the
renovate/npm-body-parser-vulnerability
branch
from
April 8, 2026 19:46
a270256 to
a6c492c
Compare
renovate
Bot
force-pushed
the
renovate/npm-body-parser-vulnerability
branch
2 times, most recently
from
April 27, 2026 23:47
a6c492c to
2bdaa01
Compare
renovate
Bot
force-pushed
the
renovate/npm-body-parser-vulnerability
branch
2 times, most recently
from
June 1, 2026 23:12
20b8082 to
759fc25
Compare
renovate
Bot
force-pushed
the
renovate/npm-body-parser-vulnerability
branch
from
June 11, 2026 14:51
759fc25 to
51a390c
Compare
renovate
Bot
force-pushed
the
renovate/npm-body-parser-vulnerability
branch
from
July 21, 2026 10:44
51a390c to
21fcf92
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.2→1.20.6body-parser vulnerable to denial of service when url encoding is enabled
CVE-2024-45590 / GHSA-qwcr-r2fm-qrc7
More information
Details
Impact
body-parser <1.20.3 is vulnerable to denial of service when url encoding is enabled. A malicious actor using a specially crafted payload could flood the server with a large number of requests, resulting in denial of service.
Patches
this issue is patched in 1.20.3
References
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
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
===================
v1.20.3Compare Source
===================
depthoption to customize the depth level in the parserdepthlevel for parsing URL-encoded data is now32(previously wasInfinity)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.