Repository navigation
Update dependency body-parser to v1.20.6 [SECURITY] - #62
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[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
December 2, 2024 09:52
0adc4eb to
499b120
Compare
renovate
Bot
force-pushed
the
renovate/npm-body-parser-vulnerability
branch
from
January 23, 2025 17:45
499b120 to
f727f2b
Compare
renovate
Bot
force-pushed
the
renovate/npm-body-parser-vulnerability
branch
from
February 9, 2025 12:48
f727f2b to
d193449
Compare
renovate
Bot
force-pushed
the
renovate/npm-body-parser-vulnerability
branch
from
March 3, 2025 15:35
d193449 to
2cc9706
Compare
renovate
Bot
force-pushed
the
renovate/npm-body-parser-vulnerability
branch
from
March 11, 2025 13:04
2cc9706 to
50dc6df
Compare
renovate
Bot
force-pushed
the
renovate/npm-body-parser-vulnerability
branch
2 times, most recently
from
March 30, 2026 21:45
50dc6df to
8c8e537
Compare
renovate
Bot
force-pushed
the
renovate/npm-body-parser-vulnerability
branch
from
April 8, 2026 17:56
8c8e537 to
266af53
Compare
renovate
Bot
force-pushed
the
renovate/npm-body-parser-vulnerability
branch
2 times, most recently
from
April 27, 2026 23:41
266af53 to
9c3882c
Compare
renovate
Bot
force-pushed
the
renovate/npm-body-parser-vulnerability
branch
2 times, most recently
from
June 1, 2026 23:14
6463d81 to
c9e4459
Compare
renovate
Bot
force-pushed
the
renovate/npm-body-parser-vulnerability
branch
from
June 11, 2026 20:07
c9e4459 to
f4dab23
Compare
renovate
Bot
force-pushed
the
renovate/npm-body-parser-vulnerability
branch
from
August 26, 2026 20:42
f4dab23 to
5a850a5
Compare
renovate
Bot
force-pushed
the
renovate/npm-body-parser-vulnerability
branch
from
October 22, 2026 13:46
5a850a5 to
7e0a1d1
Compare
renovate
Bot
force-pushed
the
renovate/npm-body-parser-vulnerability
branch
from
November 2, 2026 13:02
7e0a1d1 to
f7f3e03
Compare
This branch has not been deployed
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.18.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
======
limitoption validation (#698)limitvalues (e.g. unparseable strings orNaN) now throw instead of being silently ignored, which previously disabled size limit enforcementnullandundefinedfall back to the default 100kb limitv1.20.5Compare Source
======
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)v1.20.2Compare Source
======
v1.20.1Compare Source
======
v1.20.0Compare Source
======
strictevalusage withFunctionconstructorprocessto check for listenersv1.19.2Compare Source
======
__proto__keysv1.19.1Compare Source
======
v1.19.0Compare Source
======
pb) supportthrowon invalid typev1.18.3Compare 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.