Approved changes feed: RSS · Atom

cpe:2.3:a:openjsf:express:*:*:*:*:*:node.js:*:*

part: a version: * update: *

VendorOpenjsf (e371b9eb-ab86-58dc-866f-7af8b12292ef)
ProductExpress (6237d38e-999e-5748-8dcf-29e89cf0ec1f)
Edition*
Language*
Software edition*
Target softwarenode.js
Target hardware*
Other*
NotesImported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:deb/debian/node-express purl2cpe 2026-06-01 10:14:22.236284
pkg:deb/ubuntu/node-express purl2cpe 2026-06-01 10:14:22.236285
pkg:github/expressjs/express purl2cpe 2026-06-01 10:14:22.236287
pkg:maven/org.webjars.npm/express purl2cpe 2026-06-01 10:14:22.236288
pkg:npm/express purl2cpe 2026-06-01 10:14:22.236290

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2024-43796 vulnerable 2026-06-08 06:45:53.053752 express vulnerable to XSS via response.redirect()
MEDIUM (5)
Express.js minimalist web framework for node. In express < 4.20.0, passing untrusted user input - even after sanitizing it - to response.redirect() may execute untrusted code. This issue is patched in express 4.20.0.
Published: 2024-09-10T14:36:27.380Z
Updated: 2024-09-10T15:58:45.956Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-29041 vulnerable 2026-06-08 06:33:28.477294 Express.js Open Redirect in malformed URLs
MEDIUM (6.1)
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.
Published: 2024-03-25T20:20:06.205Z
Updated: 2024-08-02T01:03:51.705Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-10491 vulnerable 2026-06-08 06:23:46.748342 Preload arbitrary resources by injecting additional `Link` headers
MEDIUM (4)
A vulnerability has been identified in the Express response.links function, allowing for arbitrary resource injection in the Link header when unsanitized data is used. The issue arises from improper sanitization in `Link` header values, which can allow a combination of characters like `,`, `;`, and `<>` to preload malicious resources. This vulnerability is especially relevant for dynamic parameters.
Published: 2024-10-29T16:23:21.219Z
Updated: 2024-10-29T19:44:30.890Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2022-24999 vulnerable 2026-06-08 05:41:45.082033 Details available
qs before 6.10.3, as used in Express before 4.17.3 and other products, allows attackers to cause a Node process hang for an Express application because an __ proto__ key can be used. In many typical Express use cases, an unauthenticated remote attacker can place the attack payload in the query string of the URL that is used to visit the application, such as a[__proto__]=b&a[__proto__]&a[length]=100000000. The fix was backported to qs 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, and 6.2.4 (and therefore Express 4.17.3, which has "deps: qs@6.9.7" in its release description, is not vulnerable).
Published: 2022-11-26T00:00:00.000Z
Updated: 2025-04-29T13:56:42.673Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.