npm package
express 4.10.3 vulnerabilities
OSV.dev didn’t answer just now, so we can’t say whether express 4.10.3 has known vulnerabilities. This page checks again within the hour.
npm (opens in a new tab) describes it as “Fast, unopinionated, minimalist web framework”
- Known vulnerabilities
- Not checked
- OSV.dev didn’t answer
- Released
- Nov 24, 2014
- Latest is 5.3.0
- Downloads last week
- 46
- Under 1% of express downloads
- Express 4 support
- Supported
- Licence
- MIT
- Pulls in
- 35 packages
- Resolved by deps.dev
What to upgrade to
4.22.3 is the closest release with no known vulnerabilities that we checked.
4.22.3Upgrade to this
Newest 4.x release. Released Sep 14, 2026.
No known vulnerabilitiesLatest release. Released Oct 9, 2026.
No known vulnerabilities
4.22.3 came out on Sep 14, 2026. A coding agent trained before then doesn’t know it exists, so it may suggest an older release. AI knowledge cutoff dates
Findings
- LowOutdated
express 4.10.3 is 1 major version behind
Latest release is 5.3.0.
Who is still on a vulnerable express
6% of last week’s 87.3M 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.
How this page is checked
StackPrism asks OSV.dev which advisories affect exactly express 4.10.3, 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 (didn’t answer), deps.dev and endoflife.date. Findings from that source may be missing; this page refreshes soon.