Vulnerability · CVE-2024-29041
Express.js Open Redirect in malformed URLs
Published Mar 25, 2024 · catalog updated Mar 25, 2024 · Express.js Open Redirect in
Last checked Nov 8, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2024-29041. EPSS is 0.79%. Act only if a listed version of Express.js Open Redirect in is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (Express.js Open Redirect in).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Medium6.1
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.79%
- Remediation
- Version ranges on file
- Affected products
- cpe openjsf/express · npm express
### 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 ](https://github.com/pillarjs/encodeurl) on the contents before passing it to the header. 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 but this is also called from within . ### Patches https://github.com/expressjs/express/commit/0867302ddbde0e9463d0564fea5861feb708c2dd https://github.com/expressjs/express/commit/0b746953c4bd8e377123527db11f9cd866e39f94 An initial fix went out with , we then patched a feature regression in and added improved handling for the bypass in . ### Workarounds The fix for this involves pre-parsing the url string with either or . These are steps you can take on your own before passing the user input string to or . ### References https://github.com/expressjs/express/pull/5539 https://github.com/koajs/koa/issues/1800 https://expressjs.com/en/4x/api.html#res.location
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- cpe openjsf/express5.0.0
- cpe openjsf/express< 4.19.2
- npm express<4.19.2
- npm express>=5.0.0-alpha.1, <5.0.0-beta.3
How to fix CVE-2024-29041
Upgrade
CVE-2024-29041 lists a fix boundary at 4.19.2. Compare the installed build with that boundary before you change production.
Version check
Affected < 4.19.2
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2024-29041. EPSS is 0.79%. Act only if a listed version of Express.js Open Redirect in is installed.
Which versions are affected?
Compare what you have installed with 5.0.0, < 4.19.2, <4.19.2, >=5.0.0-alpha.1, <5.0.0-beta.3. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-1286; CWE-601: URL Redirection to Untrusted Site (Open Redirect). EPSS 0.79%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Mar 25, 2024 · Maintainer security tabs
Detected
### 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 ](https://github.com/pillarjs/encodeurl) on the contents before passing it to the header. This can cause malformed URL
Mar 25, 2024 · Maintainer security tabs
Updated
### 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 ](https://github.com/pillarjs/encodeurl) on the contents before passing it to the header. This can cause malformed URL
Sources
- CVE.orgVulnerability recordCVE-2024-29041
Official CVE identifier
cve.org - Maintainer security tabsVendor advisoryGHSA-rv95-896h-c2vc
### 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 ](https://github.com/pillarjs/encodeurl) on the contents before passing it to the header. This can cause malformed URL
github.com - Monitored products — highVendor advisoryCVE-2024-29041
Express.js minimalist web framework for node. Versions of Express.js prior to 4.19.0 and all pre-release alpha and beta versions of 5.0 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 ](https://github.com/pillarjs/encodeurl) on the contents before passing it to the header. Th
nvd.nist.gov
References
Freshness
Last verified in this catalog Nov 8, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- Monitored products — highNov 8, 2026
- CVE.orgNov 4, 2026
- Maintainer security tabsNov 2, 2026