Update dependency express to v4.20.0 [SECURITY] - #77
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
September 19, 2024 22:40
455bc8e to
d0805a9
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
August 10, 2025 13:00
d0805a9 to
87204e5
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
September 25, 2025 20:10
87204e5 to
7b7451d
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
February 12, 2026 13:58
7b7451d to
e3939da
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
2 times, most recently
from
April 1, 2026 17:37
e3939da to
e631ce2
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
April 8, 2026 21:11
e631ce2 to
9211491
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
2 times, most recently
from
April 16, 2026 17:09
9211491 to
868e8f8
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
2 times, most recently
from
April 29, 2026 11:55
868e8f8 to
6f55186
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
2 times, most recently
from
June 1, 2026 18:34
ff038c4 to
ec810ef
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
June 11, 2026 13:47
ec810ef to
9e7ed80
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:
4.18.2→4.20.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Express.js Open Redirect in malformed URLs
CVE-2024-29041 / GHSA-rv95-896h-c2vc
More information
Details
Impact
Versions of Express.js prior to 4.19.2 and pre-release alpha and beta versions before 5.0.0-beta.3 are affected by an open redirect vulnerability using malformed URLs.
When a user of Express performs a redirect using a user-provided URL Express performs an encode using
encodeurlon the contents before passing it to thelocationheader. This can cause malformed URLs to be evaluated in unexpected ways by common redirect allow list implementations in Express applications, leading to an Open Redirect via bypass of a properly implemented allow list.The main method impacted is
res.location()but this is also called from withinres.redirect().Patches
expressjs/express@0867302
expressjs/express@0b74695
An initial fix went out with
express@4.19.0, we then patched a feature regression in4.19.1and added improved handling for the bypass in4.19.2.Workarounds
The fix for this involves pre-parsing the url string with either
require('node:url').parseornew URL. These are steps you can take on your own before passing the user input string tores.locationorres.redirect.Resources
https://github.com/expressjs/express/pull/5539
https://github.com/koajs/koa/issues/1800
https://expressjs.com/en/4x/api.html#res.location
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
express vulnerable to XSS via response.redirect()
CVE-2024-43796 / GHSA-qw6h-vgh9-j6wx
More information
Details
Impact
In express <4.20.0, passing untrusted user input - even after sanitizing it - to
response.redirect()may execute untrusted codePatches
this issue is patched in express 4.20.0
Workarounds
users are encouraged to upgrade to the patched version of express, but otherwise can workaround this issue by making sure any untrusted inputs are safe, ideally by validating them against an explicit allowlist
Details
successful exploitation of this vector requires the following:
Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:LReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
expressjs/express (express)
v4.20.0Compare Source
==========
depthoption to customize the depth level in the parserdepthlevel for parsing URL-encoded data is now32(previously wasInfinity)res.redirect\,|, and^to align better with URL specoptions.maxAgeandoptions.expirestores.clearCookiev4.19.2Compare Source
==========
v4.19.1Compare Source
==========
v4.19.0Compare Source
==========
v4.18.3Compare Source
==========
partitionedoptionConfiguration
📅 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.