VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

express: vulnerability history, versions and safety

express is a package in the npm ecosystem. Vulert records 6 vulnerabilities for it across 99 releases, from Oct 2018 to Dec 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
6 vulnerabilities recorded M3 L3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 01 Dec 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all express vulnerabilities

Vulert verdict on express 5.3.0 i

Updated on 23 Oct 2026

Good news: 5.3.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 6.

Package health score 90/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Stay on 5.3.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 5.3.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 5.3.0 — unaffected i
  • Vulnerabilities on record 6 over 7 years · 1 in the last year i
  • Latest disclosure 01 Dec 2025 i
  • Highest CVSS 6.1 i
  • With no published fix 0 i
  • Depended on by 108,172 packages i
  • Stars 69,575 i
  • OpenSSF scorecard 6/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for express, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
5.3.0 09 Oct 2026 none MIT — Details →
4.22.3 14 Sep 2026 none MIT — Details →
4.22.2 11 May 2026 none MIT — Details →
4.22.1 01 Dec 2025 none MIT — Details →
5.2.1 01 Dec 2025 none MIT — Details →
5.2.0 01 Dec 2025 none MIT — Details →
4.22.0 01 Dec 2025 none MIT — Details →
5.1.0 31 Mar 2025 none MIT — Details →
4.21.2 05 Dec 2024 L1 MIT Yes Details →
5.0.1 08 Oct 2024 none MIT — Details →
4.21.1 08 Oct 2024 L1 MIT Yes Details →
4.21.0 11 Sep 2024 L1 MIT Yes Details →
5.0.0 10 Sep 2024 none MIT — Details →
4.20.0 10 Sep 2024 L1 MIT Yes Details →
5.0.0-beta.3 25 Mar 2024 none MIT — Details →
4.19.2 25 Mar 2024 L2 MIT Yes Details →
5.0.0-beta.2 21 Mar 2024 none MIT — Details →
4.19.1 20 Mar 2024 M1 L2 MIT Yes Details →
4.19.0 20 Mar 2024 M1 L2 MIT Yes Details →
4.18.3 29 Feb 2024 M1 L2 MIT Yes Details →
4.18.2 08 Oct 2022 M1 L2 MIT Yes Details →
4.18.1 29 Apr 2022 M1 L2 MIT Yes Details →
4.18.0 25 Apr 2022 M1 L2 MIT Yes Details →
4.17.3 17 Feb 2022 M1 L2 MIT Yes Details →
5.0.0-beta.1 15 Feb 2022 none MIT — Details →
4.17.2 17 Dec 2021 M1 L2 MIT Yes Details →
5.0.0-alpha.8 26 Mar 2020 none MIT — Details →
4.17.1 26 May 2019 M1 L2 MIT Yes Details →
4.17.0 17 May 2019 M1 L2 MIT Yes Details →
5.0.0-alpha.7 27 Oct 2018 none MIT — Details →
4.16.4 11 Oct 2018 M1 L2 MIT Yes Details →
4.16.3 12 Mar 2018 M1 L2 MIT Yes Details →
4.16.2 10 Oct 2017 M1 L2 MIT Yes Details →
4.16.1 29 Sep 2017 M1 L2 MIT Yes Details →
4.16.0 28 Sep 2017 M1 L2 MIT Yes Details →
5.0.0-alpha.6 25 Sep 2017 none MIT — Details →
4.15.5 25 Sep 2017 M1 L2 MIT Yes Details →
4.15.4 07 Aug 2017 M1 L2 MIT Yes Details →
4.15.3 17 May 2017 M1 L2 MIT Yes Details →
5.0.0-alpha.5 06 Mar 2017 none MIT — Details →
4.15.2 06 Mar 2017 M1 L2 MIT Yes Details →
4.15.1 06 Mar 2017 M1 L2 MIT Yes Details →
5.0.0-alpha.4 02 Mar 2017 none MIT — Details →
4.15.0 01 Mar 2017 M1 L2 MIT Yes Details →
5.0.0-alpha.3 29 Jan 2017 none MIT — Details →
4.14.1 28 Jan 2017 M1 L2 MIT Yes Details →
4.14.0 16 Jun 2016 M1 L2 MIT Yes Details →
4.13.4 22 Jan 2016 M1 L2 MIT Yes Details →
4.13.3 03 Aug 2015 M1 L2 MIT Yes Details →
4.13.2 31 Jul 2015 M1 L2 MIT Yes Details →
3.21.2 31 Jul 2015 M2 L3 MIT Yes Details →
5.0.0-alpha.2 07 Jul 2015 none MIT — Details →
4.13.1 06 Jul 2015 M1 L2 MIT Yes Details →
3.21.1 06 Jul 2015 M2 L3 MIT Yes Details →
4.13.0 21 Jun 2015 M1 L2 MIT Yes Details →
3.21.0 19 Jun 2015 M2 L3 MIT Yes Details →
4.12.4 18 May 2015 M1 L2 MIT Yes Details →
3.20.3 18 May 2015 M2 L3 MIT Yes Details →
4.12.3 17 Mar 2015 M1 L2 MIT Yes Details →
3.20.2 17 Mar 2015 M2 L3 MIT Yes Details →
4.12.2 03 Mar 2015 M1 L2 MIT Yes Details →
4.12.1 02 Mar 2015 M1 L2 MIT Yes Details →
3.20.1 01 Mar 2015 M2 L3 MIT Yes Details →
4.12.0 23 Feb 2015 M1 L2 MIT Yes Details →
3.20.0 19 Feb 2015 M2 L3 MIT Yes Details →
4.11.2 01 Feb 2015 M1 L2 MIT Yes Details →
3.19.2 01 Feb 2015 M2 L3 MIT Yes Details →
4.11.1 21 Jan 2015 M1 L2 MIT Yes Details →
3.19.1 21 Jan 2015 M2 L3 MIT Yes Details →
4.11.0 14 Jan 2015 M1 L2 MIT Yes Details →
4.10.8 13 Jan 2015 M1 L2 MIT Yes Details →
3.19.0 09 Jan 2015 M2 L3 MIT Yes Details →
4.10.7 05 Jan 2015 M1 L2 MIT Yes Details →
4.10.6 13 Dec 2014 M1 L2 MIT Yes Details →
3.18.6 13 Dec 2014 M2 L3 MIT Yes Details →
3.18.5 12 Dec 2014 M2 L3 MIT Yes Details →
4.10.5 11 Dec 2014 M1 L2 MIT Yes Details →
4.10.4 25 Nov 2014 M1 L2 MIT Yes Details →
4.10.3 24 Nov 2014 M1 L2 MIT Yes Details →
3.18.4 23 Nov 2014 M2 L3 MIT Yes Details →
4.10.2 10 Nov 2014 M1 L2 MIT Yes Details →
3.18.3 09 Nov 2014 M2 L3 MIT Yes Details →
5.0.0-alpha.1 07 Nov 2014 none MIT — Details →
4.10.1 29 Oct 2014 M1 L2 MIT Yes Details →
3.18.2 29 Oct 2014 M2 L3 MIT Yes Details →
4.10.0 24 Oct 2014 M1 L2 MIT Yes Details →
3.18.1 23 Oct 2014 M2 L3 MIT Yes Details →
3.18.0 18 Oct 2014 M2 L3 MIT Yes Details →
4.9.8 18 Oct 2014 M1 L2 MIT Yes Details →
3.17.8 16 Oct 2014 M2 L3 MIT Yes Details →
4.9.7 10 Oct 2014 M1 L2 MIT Yes Details →
4.9.6 09 Oct 2014 M1 L2 MIT Yes Details →
3.17.7 08 Oct 2014 M2 L3 MIT Yes Details →
3.17.6 03 Oct 2014 M2 L3 MIT Yes Details →
4.9.5 25 Sep 2014 M1 L2 MIT Yes Details →
3.17.5 24 Sep 2014 M2 L3 MIT Yes Details →
4.9.4 20 Sep 2014 M1 L2 MIT Yes Details →
3.17.4 20 Sep 2014 M2 L3 MIT Yes Details →
4.9.3 18 Sep 2014 M1 L2 MIT Yes Details →
3.17.3 18 Sep 2014 M2 L3 MIT Yes Details →
4.9.2 18 Sep 2014 M1 L2 — Yes Details →
4.9.1 17 Sep 2014 M1 L2 — Yes Details →
3.17.2 16 Sep 2014 M2 L3 — Yes Details →
4.9.0 09 Sep 2014 M1 L2 — Yes Details →
3.17.1 09 Sep 2014 M2 L3 — Yes Details →
3.17.0 09 Sep 2014 M2 L3 — Yes Details →
4.8.8 05 Sep 2014 M1 L2 — Yes Details →
3.16.10 05 Sep 2014 M2 L3 — Yes Details →
4.8.7 30 Aug 2014 M1 L2 — Yes Details →
3.16.9 30 Aug 2014 M2 L3 — Yes Details →
4.8.6 28 Aug 2014 M1 L2 — Yes Details →
3.16.8 28 Aug 2014 M2 L3 — Yes Details →
4.8.5 19 Aug 2014 M1 L2 — Yes Details →
3.16.7 19 Aug 2014 M2 L3 — Yes Details →
4.8.4 15 Aug 2014 M1 L2 — Yes Details →
3.16.6 15 Aug 2014 M2 L3 — Yes Details →
3.16.5 12 Aug 2014 M2 L3 — Yes Details →
4.8.3 11 Aug 2014 M1 L2 — Yes Details →
3.16.4 11 Aug 2014 M2 L3 — Yes Details →
3.16.3 08 Aug 2014 M2 L3 — Yes Details →

The newest 120 of 290 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1
  • 2024 4
  • 2025 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 6 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for express

The 5 most severe of 6 vulnerabilities recorded for this package

Search all 6 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2014-6393: No Charset in Content-Type Header in express 6.1 medium 3.11.0 23 Oct 2018
CVE-2024-29041: Express.js Open Redirect in malformed URLs 6.1 medium 4.19.2 25 Mar 2024
CVE-2024-43796: XSS Vulnerability in Express 5.0 low 4.20.0 10 Sep 2024
CVE-2024-9266: Express Open Redirect Vulnerability in Express Package 4.7 low 4.0.0-rc1 03 Oct 2024
Express ressource injection 4.0 medium 4.0.0-rc1 29 Oct 2024

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About express

Is express safe to use?

Vulert records 6 vulnerabilities for express in npm: 0 critical, 0 high, 3 medium and 3 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is express's Vulert package health score?

Vulert scores express 90/100, which reads as healthy. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of express affected?

No. 5.3.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does express have?

6 vulnerabilities are recorded for express in the npm ecosystem: 0 critical, 0 high, 3 medium and 3 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new express vulnerabilities disclosed?

1 vulnerability was recorded for express in the last 12 months, and the oldest entry in this database dates to 23 Oct 2018. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of express are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor express for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the express version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.