Express.js Open Redirect in malformed URLs
cve-program · CVE-2024-29041
PublishedExpress.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 `encodeurl`](https://github.com/pillarjs/encodeurl) on the contents before passing it to the `location` 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 `res.location()` but this is also called from within `res.redirect()`. The vulnerability is fixed in 4.19.2 and 5.0.0-beta.3.
Read the publisher's advisoryeuvd · EUVD-2024-1007
PublishedExpress.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 `encodeurl`](https://github.com/pillarjs/encodeurl) on the contents before passing it to the `location` 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 `res.location()` but this is also called from within `res.redirect()`. The vulnerability is fixed in 4.19.2 and 5.0.0-beta.3.
Read the publisher's advisorynvd · CVE-2024-29041
PublishedExpress.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 `encodeurl`](https://github.com/pillarjs/encodeurl) on the contents before passing it to the `location` 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 `res.location()` but this is also called from within `res.redirect()`. The vulnerability is fixed in 4.19.2 and 5.0.0-beta.3.
Read the publisher's advisoryosv · GHSA-rv95-896h-c2vc
Published### 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 `encodeurl`](https://github.com/pillarjs/encodeurl) on the contents before passing it to the `location` 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 `res.location()` but this is also called from within `res.redirect()`. ### Patches https://github.com/expressjs/express/commit/0867302ddbde0e9463d0564fea5861feb708c2dd https://github.com/expressjs/express/commit/0b746953c4bd8e377123527db11f9cd866e39f94 An initial fix went out with `[email protected]`, we then patched a feature regression in `4.19.1` and added improved handling for the bypass in `4.19.2`. ### Workarounds The fix for this involves pre-parsing the url string with either `require('node:url').parse` or `new URL`. These are steps you can take on your own before passing the user input string to `res.location` or `res.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
Read the publisher's advisoryAffected versions, risk and source history
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
cve-program · CVE-2024-29041
PublishedExpress.js Open Redirect in malformed URLs
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 `encodeurl`](https://github.com/pillarjs/encodeurl) on the contents before passing it to the `location` 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 `res.location()` but this is also called from within `res.redirect()`. The vulnerability is fixed in 4.19.2 and 5.0.0-beta.3.
- Source published
- 25 Mar 2024 20:20:06 UTC
- Source modified
- 2 Aug 2024 01:03:51 UTC
- Saved here
- 23 Oct 2026 15:48:27 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
euvd · EUVD-2024-1007
PublishedExpress.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 r…
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 `encodeurl`](https://github.com/pillarjs/encodeurl) on the contents before passing it to the `location` 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 `res.location()` but this is also called from within `res.redirect()`. The vulnerability is fixed in 4.19.2 and 5.0.0-beta.3.
Additional publisher context
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Mar 25, 2024, 8:20:06 PM
dateUpdated: Aug 2, 2024, 1:03:51 AM
18 related source bulletins · separate from aliases
RHSA-2025:8544: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.15.14 Bug Fix Update
CVE-2024-11831 · CVE-2024-21536 · CVE-2024-21538 · CVE-2024-29041 · CVE-2024-29180 · CVE-2024-37890 · CVE-2024-39249 · CVE-2024-45338 · CVE-2024-45590 · CVE-2024-48910 · CVE-2025-22868 · CVE-2025-30204
RHSA-2024:4873: Red Hat Security Advisory: Apicurio Registry (container images) release and security update [ 2.6.1 GA ]
CVE-2023-51775 · CVE-2024-2700 · CVE-2024-22201 · CVE-2024-29041 · CVE-2024-29180
RHSA-2025:4511: Red Hat Security Advisory: RHODF-4.18-RHEL-9 security update
CVE-2024-11831 · CVE-2024-21536 · CVE-2024-29041 · CVE-2025-22868 · CVE-2025-22869 · CVE-2025-27144 · CVE-2025-30204
WID-SEC-W-2024-1590: HCL BigFix: Mehrere Schwachstellen
CVE-2024-33883 · CVE-2023-42282 · CVE-2024-29041 · CVE-2021-43306 · CVE-2022-31147
RHEA-2024:7870: Red Hat Enhancement Advisory: Red Hat OpenShift Pipelines Operator Bundle 1.16.0 release
CVE-2024-28863 · CVE-2024-29041 · CVE-2024-29180 · CVE-2024-39338
msrc_CVE-2024-29041: Express.js Open Redirect in malformed URLs
CVE-2024-29041
WID-SEC-W-2025-0010: HCL BigFix Server Automation: Mehrere Schwachstellen
CVE-2023-26159 · CVE-2024-28849 · CVE-2024-29041
NCSC-2025-0026: Kwetsbaarheden verholpen in Oracle JD Edwards
CVE-2023-2976 · CVE-2023-3961 · CVE-2023-4091 · CVE-2023-4782 · CVE-2023-5678 · CVE-2023-6129 · CVE-2023-38552 · CVE-2023-39017 · CVE-2023-42669 · CVE-2023-48795 · CVE-2024-0727 · CVE-2024-21245 · CVE-2024-22019 · CVE-2024-22020 · CVE-2024-27280 · CVE-2024-27281 · CVE-2024-27282 · CVE-2024-27983 · CVE-2024-29041 · CVE-2025-21507 · CVE-2025-21508 · CVE-2025-21509 · CVE-2025-21510 · CVE-2025-21511 · CVE-2025-21512 · CVE-2025-21513 · CVE-2025-21514 · CVE-2025-21515 · CVE-2025-21517 · CVE-2025-21524 · CVE-2025-21527 · CVE-2025-21538 · CVE-2025-21552
RHSA-2025:8551: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.14.18 Bug Fix Update
CVE-2024-11831 · CVE-2024-21536 · CVE-2024-21538 · CVE-2024-29041 · CVE-2024-29180 · CVE-2024-37890 · CVE-2024-39249 · CVE-2024-45338 · CVE-2024-45590 · CVE-2024-48910
RHSA-2025:8479: Red Hat Security Advisory: RHODF-4.16-RHEL-9 security update
CVE-2024-11831 · CVE-2024-21536 · CVE-2024-29041 · CVE-2024-39249 · CVE-2024-45338 · CVE-2024-45590 · CVE-2025-30204
WID-SEC-W-2025-0168: Oracle JD Edwards: Mehrere Schwachstellen
CVE-2023-2976 · CVE-2023-3961 · CVE-2023-4782 · CVE-2023-48795 · CVE-2023-6129 · CVE-2024-21245 · CVE-2024-27280 · CVE-2024-27983 · CVE-2024-29041 · CVE-2025-21507 · CVE-2025-21508 · CVE-2025-21509 · CVE-2025-21510 · CVE-2025-21511 · CVE-2025-21512 · CVE-2025-21513 · CVE-2025-21514 · CVE-2025-21515 · CVE-2025-21517 · CVE-2025-21524 · CVE-2025-21527 · CVE-2025-21538 · CVE-2025-21552
WID-SEC-W-2024-0956: IBM App Connect Enterprise: Mehrere Schwachstellen
CVE-2024-29041 · CVE-2024-30260 · CVE-2024-30261
RHSA-2025:8059: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.17.7 Bug Fix Update
CVE-2024-11831 · CVE-2024-21536 · CVE-2024-29041 · CVE-2024-39249 · CVE-2024-45338 · CVE-2024-45590 · CVE-2025-27144 · CVE-2025-30204
WID-SEC-W-2024-2036: Red Hat OpenShift: Mehrere Schwachstellen ermöglichen Umgehen von Sicherheitsvorkehrungen
CVE-2024-29041 · CVE-2024-39338 · CVE-2024-4067 · CVE-2024-4068
RHSA-2024:3868: Red Hat Security Advisory: Network Observability 1.6.0 for OpenShift
CVE-2023-39326 · CVE-2023-42282 · CVE-2023-45289 · CVE-2023-45290 · CVE-2024-24783 · CVE-2024-24785 · CVE-2024-24786 · CVE-2024-28849 · CVE-2024-29041 · CVE-2024-29180
RHSA-2024:6211: Red Hat Security Advisory: Red Hat OpenShift Service Mesh Containers for 2.6.1 security update
CVE-2024-4067 · CVE-2024-4068 · CVE-2024-29041 · CVE-2024-39338
RHSA-2024:7164: Red Hat Security Advisory: Migration Toolkit for Containers (MTC) 1.8.4 security and bug fix update
CVE-2019-25211 · CVE-2023-45288 · CVE-2023-45289 · CVE-2024-3727 · CVE-2024-4068 · CVE-2024-24788 · CVE-2024-28180 · CVE-2024-28849 · CVE-2024-28863 · CVE-2024-29018 · CVE-2024-29041 · CVE-2024-29180 · CVE-2024-39338
RHSA-2024:7624: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.14.11 security and bug fix update
CVE-2024-6104 · CVE-2024-29041 · CVE-2024-41818
- Source published
- Mar 25, 2024, 8:20:06 PM (timezone not stated)
- Source modified
- Aug 2, 2024, 1:03:51 AM (timezone not stated)
- Saved here
- 15 Nov 2026 07:46:33 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
EUVD CVSS 3.1 · 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
nvd · CVE-2024-29041
PublishedExpress.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 r…
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 `encodeurl`](https://github.com/pillarjs/encodeurl) on the contents before passing it to the `location` 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 `res.location()` but this is also called from within `res.redirect()`. The vulnerability is fixed in 4.19.2 and 5.0.0-beta.3.
Additional publisher context
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Analyzed
Weakness classifications: CWE-601 · CWE-1286
Original publisher date fields
published: 2024-03-25T21:15:46.847
lastModified: 2026-06-17T07:22:18.493
11 source CPE criteria · context only
- cpe:2.3:a:openjsf:express:*:*:*:*:*:node.js:*:*
- cpe:2.3:a:openjsf:express:5.0.0:alpha1:*:*:*:node.js:*:*
- cpe:2.3:a:openjsf:express:5.0.0:alpha2:*:*:*:node.js:*:*
- cpe:2.3:a:openjsf:express:5.0.0:alpha3:*:*:*:node.js:*:*
- cpe:2.3:a:openjsf:express:5.0.0:alpha4:*:*:*:node.js:*:*
- cpe:2.3:a:openjsf:express:5.0.0:alpha5:*:*:*:node.js:*:*
- cpe:2.3:a:openjsf:express:5.0.0:alpha6:*:*:*:node.js:*:*
- cpe:2.3:a:openjsf:express:5.0.0:alpha7:*:*:*:node.js:*:*
- cpe:2.3:a:openjsf:express:5.0.0:alpha8:*:*:*:node.js:*:*
- cpe:2.3:a:openjsf:express:5.0.0:beta1:*:*:*:node.js:*:*
- cpe:2.3:a:openjsf:express:5.0.0:beta2:*:*:*:node.js:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
- Source published
- 25 Mar 2024 21:15:46 UTC
- Source modified
- 17 Jun 2026 07:22:18 UTC
- Saved here
- 24 Oct 2026 23:17:34 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · [email protected] · Secondary · 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
osv · GHSA-rv95-896h-c2vc
PublishedExpress.js Open Redirect in malformed URLs
### 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 `encodeurl`](https://github.com/pillarjs/encodeurl) on the contents before passing it to the `location` 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 `res.location()` but this is also called from within `res.redirect()`. ### Patches https://github.com/expressjs/express/commit/0867302ddbde0e9463d0564fea5861feb708c2dd https://github.com/expressjs/express/commit/0b746953c4bd8e377123527db11f9cd866e39f94 An initial fix went out with `[email protected]`, we then patched a feature regression in `4.19.1` and added improved handling for the bypass in `4.19.2`. ### Workarounds The fix for this involves pre-parsing the url string with either `require('node:url').parse` or `new URL`. These are steps you can take on your own before passing the user input string to `res.location` or `res.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
- Source published
- 25 Mar 2024 19:40:26 UTC
- Source modified
- 10 Sep 2026 03:50:10 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Publisher rating · MODERATE