Repository navigation
chore(deps): update dependency express to v4.20.0 [security] - #80
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-express-vulnerability
branch
from
May 6, 2024 16:22
04fe1ba to
5b254df
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
3 times, most recently
from
May 27, 2024 15:18
32f42a2 to
21883ca
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
5 times, most recently
from
June 12, 2024 18:41
928d9a4 to
1b1873b
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
July 8, 2024 14:00
1b1873b to
6d3a88c
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
September 18, 2024 17:02
6d3a88c to
7e7b312
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
October 9, 2024 10:56
7e7b312 to
55411af
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
January 23, 2025 20:30
55411af to
5509fe8
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
February 7, 2025 15:38
5509fe8 to
fbda9ee
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
March 3, 2025 15:46
fbda9ee to
fc45e9f
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
March 11, 2025 11:56
fc45e9f to
f605485
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
October 21, 2025 17:59
f605485 to
81a544c
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
December 1, 2025 21:58
81a544c to
46e2ad9
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
December 31, 2025 13:08
46e2ad9 to
dd36884
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
February 12, 2026 10:47
dd36884 to
b55ba8e
Compare
auto-merge was automatically disabled
March 27, 2026 01:43
Pull request was closed
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
2 times, most recently
from
March 30, 2026 18:02
b55ba8e to
e7c151f
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
April 8, 2026 21:32
e7c151f to
bba34c7
Compare
auto-merge was automatically disabled
April 27, 2026 17:17
Pull request was closed
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
2 times, most recently
from
April 27, 2026 21:44
bba34c7 to
8fbe90a
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
2 times, most recently
from
May 18, 2026 15:10
4a36e99 to
3ffe458
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
May 28, 2026 18:51
3ffe458 to
8eec9ed
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
June 11, 2026 21:16
8eec9ed to
67f624a
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
July 12, 2026 16:18
67f624a to
51b55cf
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
2 times, most recently
from
September 15, 2026 10:39
07b142f to
efc8aba
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
3 times, most recently
from
October 26, 2026 18:25
9bbea96 to
464f801
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
November 2, 2026 20:51
464f801 to
daee57c
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.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
======
partitionedoptionConfiguration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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.