npm package
path-to-regexp 1.0.0 vulnerability, and the version that fixes it
path-to-regexp 1.0.0 has 1 known vulnerability (1 rated high or critical); 1.9.0 fixes it.
npm (opens in a new tab) describes it as “Express style path to RegExp utility”
- Known vulnerabilities
- 1
- 1 rated high or critical
- Released
- Aug 17, 2014
- Latest is 8.4.2
- Downloads last week
- 59
- Under 1% of path-to-regexp downloads
- Licence
- MIT
- Dependencies
- None
- Resolved by deps.dev
What to upgrade to
1.9.0 is the closest release with no known vulnerabilities.
1.9.0Upgrade to this
Fixes the known vulnerability and the newest 1.x release. Released Sep 10, 2024.
No known vulnerabilitiesLatest release. Released Apr 1, 2026.
No known vulnerabilities
Hand the fix to your coding agent
One task with the upgrade, the file to change and why. Paste it into Claude Code, Cursor or Codex.
Findings
- CriticalVulnerability
CVE-2024-45296 in path-to-regexp 1.0.0
EPSS: top 41%path-to-regexp outputs backtracking regular expressions. Fixed in 1.9.0.
- WarningOutdated
path-to-regexp 1.0.0 is 7 major versions behind
Latest release is 8.4.2.
- LowOpenSSF Scorecard
component/path-to-regexp scores 2/10 on OpenSSF Scorecard
Weakest checks: Not actively maintained (Maintained 0/10); Little code review (Code-Review 0/10); No branch protection (Branch-Protection 0/10). A low score means weaker upstream security practices, not a known vulnerability.
Every advisory for path-to-regexp 1.0.0
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.
CriticalCVE-2024-45296 on OSV.dev (opens in a new tab)CVE-2026-4867EPSS: top 41%
path-to-regexp outputs backtracking regular expressions
Fixed in 1.9.0. Published Sep 9, 2024.
Who is still on a vulnerable path-to-regexp
24% of last week’s 236.2M path-to-regexp 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 path-to-regexp 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 path-to-regexp 1.0.0, 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. 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 and FIRST EPSS.