StackPrism

npm package

express 4.19.2 vulnerability, and the version that fixes it

express 4.19.2 has 1 known vulnerability; 4.20.0 fixes it.

npm (opens in a new tab) describes it as “Fast, unopinionated, minimalist web framework”

Known vulnerabilities
1
None rated high or critical
Released
Mar 25, 2024
Latest is 5.3.0
Downloads last week
1.8M
1% of express downloads
Express 4 support
Supported
Licence
MIT
OpenSSF Scorecard
8.5/10
expressjs/express (opens in a new tab)
Pulls in
70 packages
Resolved by deps.dev

What to upgrade to

4.20.0 is the closest release with no known vulnerabilities.

  • 4.20.0Upgrade to this

    Fixes the known vulnerability. Released Sep 10, 2024.

    No known vulnerabilities

  • 4.22.3

    Newest 4.x release. Released Sep 14, 2026.

    No known vulnerabilities

  • 5.3.0

    Latest release. Released Oct 9, 2026.

    No known vulnerabilities

Findings

Every advisory for express 4.19.2

Known exploited first (CISA KEV), then by how likely they are to be exploited (FIRST EPSS), then by severity. Each id links to its OSV.dev record.

  1. LowCVE-2024-43796 on OSV.dev (opens in a new tab)GHSA-qw6h-vgh9-j6wxEPSS: top 60%

    express vulnerable to XSS via response.redirect()

    Fixed in 4.20.0. Published Sep 10, 2024.

Who is still on a vulnerable express

7% of last week’s 145.2M express downloads went to versions with known vulnerabilities.

From npm’s per-version download counts for the last 7 days, each version checked against OSV.dev. The versions checked cover over 99% of downloads.

Is express the only one?

Paste a public GitHub repo or drop your package.json and see every vulnerable, end-of-life or deprecated dependency, with one fix task. Free, no sign-up.

Check your whole repo

How this page is checked

StackPrism asks OSV.dev which advisories affect exactly express 4.19.2, merges duplicates filed under several ids, and ranks them with CISA’s Known Exploited Vulnerabilities list and FIRST EPSS. Release dates and deprecation come from deps.dev and npm, support dates from endoflife.date. No AI writes this page: every sentence comes from that data, refreshed every few hours.

Last checked against npm, OSV.dev, deps.dev, CISA KEV, FIRST EPSS and endoflife.date.