chore(deps): update dependency express to v4.20.0 [security] - #178
Open
renovate[bot] wants to merge 1 commit into
Open
chore(deps): update dependency express to v4.20.0 [security]#178renovate[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
January 23, 2025 20:42
b56cda6 to
58c3b88
Compare
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
January 30, 2025 17:10
58c3b88 to
9a847fd
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
February 9, 2025 17:50
9a847fd to
0609caf
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
March 3, 2025 17:11
0609caf to
e40e8db
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
March 11, 2025 11:14
e40e8db to
c1274e1
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
March 13, 2025 15:21
c1274e1 to
9ca16f5
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
March 17, 2025 17:23
9ca16f5 to
84e341a
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
April 1, 2025 13:37
84e341a to
00ce931
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
April 8, 2025 12:45
00ce931 to
a55db25
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
April 24, 2025 09:00
a55db25 to
cc0a473
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
May 19, 2025 16:58
cc0a473 to
7e90206
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
May 28, 2025 12:51
7e90206 to
ea11487
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
June 4, 2025 10:27
ea11487 to
b7391e6
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
June 22, 2025 15:24
b7391e6 to
2a079a5
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
September 25, 2025 15:31
9f6c472 to
738974c
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
October 21, 2025 15:06
738974c to
baebec8
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
October 21, 2025 15:14
baebec8 to
464e069
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
November 11, 2025 00:02
464e069 to
de1d188
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
November 18, 2025 22:12
de1d188 to
34c6995
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
December 3, 2025 18:58
34c6995 to
1a833e3
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
December 31, 2025 14:58
1a833e3 to
61567f9
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
January 8, 2026 17:53
61567f9 to
ef6d855
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
January 19, 2026 15:38
ef6d855 to
f9456c1
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
January 23, 2026 18:50
f9456c1 to
7826fb7
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
February 2, 2026 21:32
7826fb7 to
1e7dbdf
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
February 12, 2026 10:16
1e7dbdf to
b6009c6
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
February 17, 2026 21:40
b6009c6 to
6807c4e
Compare
renovate
Bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
March 5, 2026 18:58
6807c4e to
e3969ee
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.19.0→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
==========
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.