VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

path-to-regexp: vulnerability history, versions and safety

path-to-regexp is a package in the npm ecosystem. Vulert records 6 vulnerabilities for it across 42 releases, from Sep 2024 to Mar 2026. 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 H4 M2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 27 Mar 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all path-to-regexp vulnerabilities

Vulert verdict on path-to-regexp 9.0.0 i

Updated on 23 Oct 2026

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

Package health score 78/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 9.0.0 — unaffected i
  • Vulnerabilities on record 6 over 1 year · 3 in the last year i
  • Latest disclosure 27 Mar 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 8,615 i
  • OpenSSF scorecard 5/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 path-to-regexp, 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
9.0.0 22 Oct 2026 none MIT — Details →
8.4.2 01 Apr 2026 none MIT — Details →
8.4.1 30 Mar 2026 none MIT — Details →
8.4.0 26 Mar 2026 none MIT — Details →
0.1.13 26 Mar 2026 none MIT — Details →
8.3.0 02 Sep 2025 H1 M1 MIT Yes Details →
0.1.12 05 Dec 2024 H1 MIT Yes Details →
8.2.0 26 Sep 2024 H1 M1 MIT Yes Details →
0.1.11 12 Sep 2024 H2 M1 MIT Yes Details →
6.3.0 12 Sep 2024 none MIT — Details →
3.3.0 10 Sep 2024 none MIT — Details →
1.9.0 10 Sep 2024 none MIT — Details →
7.2.0 10 Sep 2024 none MIT — Details →
8.1.0 10 Sep 2024 H1 M1 MIT Yes Details →
8.0.0 01 Sep 2024 H1 M1 MIT Yes Details →
0.1.10 01 Sep 2024 H2 M1 MIT Yes Details →
0.1.9 22 Aug 2024 H2 M1 MIT Yes Details →
7.1.0 13 Jul 2024 none MIT — Details →
7.0.0 20 Jun 2024 none MIT — Details →
6.2.2 07 Apr 2024 none MIT — Details →
0.1.8 07 Apr 2024 H2 M1 MIT Yes Details →
6.2.1 06 May 2022 none MIT — Details →
6.2.0 29 Sep 2020 none MIT — Details →
6.1.0 20 Nov 2019 none MIT — Details →
6.0.0 20 Nov 2019 none MIT — Details →
5.0.0 12 Nov 2019 none MIT — Details →
4.0.5 12 Nov 2019 none MIT — Details →
4.0.4 12 Nov 2019 none MIT — Details →
4.0.3 12 Nov 2019 none MIT — Details →
4.0.2 12 Nov 2019 none MIT — Details →
4.0.1 12 Nov 2019 none MIT — Details →
4.0.0 12 Nov 2019 none MIT — Details →
3.2.0 11 Nov 2019 none MIT — Details →
1.8.0 11 Nov 2019 H1 MIT Yes Details →
3.1.0 31 Aug 2019 none MIT — Details →
3.0.0 14 Jan 2019 none MIT — Details →
2.4.0 26 Aug 2018 none MIT — Details →
2.3.0 20 Aug 2018 none MIT — Details →
2.2.1 24 Apr 2018 none MIT — Details →
2.2.0 07 Mar 2018 none MIT — Details →
2.1.0 20 Oct 2017 none MIT — Details →
2.0.0 23 Aug 2017 none MIT — Details →
1.7.0 08 Nov 2016 H1 MIT Yes Details →
1.6.0 03 Oct 2016 H1 MIT Yes Details →
1.5.3 16 Jun 2016 H1 MIT Yes Details →
1.5.2 16 Jun 2016 H1 MIT Yes Details →
1.5.1 08 Jun 2016 H1 MIT Yes Details →
1.5.0 20 May 2016 H1 MIT Yes Details →
1.4.0 19 May 2016 H1 MIT Yes Details →
1.3.0 08 May 2016 H1 MIT Yes Details →
1.2.1 17 Aug 2015 H1 MIT Yes Details →
0.1.7 28 Jul 2015 H2 M1 MIT Yes Details →
0.1.6 19 Jun 2015 H2 M1 MIT Yes Details →
1.2.0 21 May 2015 H1 MIT Yes Details →
1.1.1 12 May 2015 H1 MIT Yes Details →
1.1.0 09 May 2015 H1 MIT Yes Details →
0.1.5 09 May 2015 H2 M1 MIT Yes Details →
0.1.4 05 Mar 2015 H2 M1 MIT Yes Details →
1.0.3 17 Jan 2015 H1 MIT Yes Details →
1.0.2 17 Dec 2014 H1 MIT Yes Details →
1.0.1 28 Aug 2014 H1 MIT Yes Details →
1.0.0 17 Aug 2014 H1 MIT Yes Details →
0.2.5 07 Aug 2014 H1 MIT Yes Details →
0.2.4 02 Aug 2014 H1 MIT Yes Details →
0.2.3 08 Jul 2014 H1 MIT Yes Details →
0.2.2 06 Jul 2014 H1 MIT Yes Details →
0.1.3 06 Jul 2014 H2 M1 MIT Yes Details →
0.2.1 11 Jun 2014 H1 MIT Yes Details →
0.2.0 10 Jun 2014 H1 MIT Yes Details →
0.1.2 10 Mar 2014 H2 M1 MIT Yes Details →
0.1.1 10 Mar 2014 H2 M1 MIT Yes Details →
0.1.0 06 Mar 2014 H2 M1 MIT Yes Details →
0.0.2 10 Feb 2013 H2 M1 MIT Yes Details →
0.0.1 01 Aug 2012 H2 M1 MIT Yes Details →

All 74 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 3
  • 2026 3

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

03 Vulnerabilities

Recorded vulnerabilities for path-to-regexp

The 5 most severe of 6 vulnerabilities recorded for this package

Search all 6 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Regular Expression Denial of Service (ReDoS) in path-to-regexp 7.5 high 1.9.0 09 Sep 2024
ReDoS Vulnerability in path-to-regexp Package: Unpatched Version 0.1.x 7.5 high 0.1.12 05 Dec 2024
CVE-2026-4867: path-to-regexp Regular Expression Denial of Service Vulnerability 7.5 high 0.1.13 27 Mar 2026
CVE-2026-4926: path-to-regexp Denial of Service via Sequential Optional Groups 7.5 high 8.4.0 27 Mar 2026
CVE-2026-4923: path-to-regexp Vulnerable to Regular Expression Denial of Service via Multiple Wildcards 5.9 medium 8.4.0 27 Mar 2026

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 path-to-regexp

Is path-to-regexp safe to use?

Vulert records 6 vulnerabilities for path-to-regexp in npm: 0 critical, 4 high, 2 medium and 0 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 path-to-regexp's Vulert package health score?

Vulert scores path-to-regexp 78/100, which reads as in good shape. 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 path-to-regexp affected?

No. 9.0.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 path-to-regexp have?

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

How often are new path-to-regexp vulnerabilities disclosed?

3 vulnerabilities were recorded for path-to-regexp in the last 12 months, and the oldest entry in this database dates to 09 Sep 2024. 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 path-to-regexp 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 path-to-regexp for upcoming vulnerabilities?

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