Update dependency express to v4.20.0 [SECURITY]#32
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
September 12, 2024 03:04
b0db9ed to
7f9d1a4
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
December 8, 2024 23:35
ec48cd3 to
7f9d1a4
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
January 23, 2025 21:25
7f9d1a4 to
a4428d2
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
February 9, 2025 12:43
a4428d2 to
c43dc75
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
March 3, 2025 16:42
c43dc75 to
ba8bd41
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
March 11, 2025 13:18
ba8bd41 to
68160c1
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
November 11, 2025 01:05
68160c1 to
863eb2b
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
November 18, 2025 19:04
863eb2b to
1409180
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
2 times, most recently
from
January 22, 2026 17:35
1409180 to
32373d8
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
2 times, most recently
from
March 30, 2026 18:17
32373d8 to
edd280b
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
April 8, 2026 20:02
edd280b to
8a7e0b7
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
2 times, most recently
from
April 27, 2026 22:30
8a7e0b7 to
a009a57
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
3 times, most recently
from
May 28, 2026 19:39
945e618 to
0ae96d6
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
June 13, 2026 16:04
0ae96d6 to
130ab74
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.17.1→4.20.0Express.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
==========
partitionedoptionv4.18.2Compare Source
===================
v4.18.1Compare Source
===================
v4.18.0Compare Source
===================
res.downloadoptionswithoutfilenameinres.downloadres.statusnull/undefinedasmaxAgeinres.cookieObject.prototypevalues in settings throughapp.set/app.getdefaultwith same arguments as types inres.formatres.sendhttp-errorsforres.formaterrorstrictpriorityoptionexpiresoption to reject invalid datesevalusage withFunctionconstructorprocessto check for listeners425 Unordered Collectionto standard425 Too Earlyv4.17.3Compare Source
===================
__proto__keysv4.17.2Compare Source
===================
undefinedinres.jsonpundefinedwhen"json escape"is enabledRegExpsres.jsonp(obj, status)deprecation messageres.isJSDocmaxAgeoption to reject invalid valuesreq.socketover deprecatedreq.connectionConfiguration
📅 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.