Is path-to-regexp 0.1 vulnerable?
npm · 14 releases from 0.1.0 to 0.1.13 · latest path-to-regexp is 9.0.0 · checked 1 Nov 2026
No known advisories in the last release
path-to-regexp 0.1.13, the last 0.1 release, has no known advisories. 3 advisories affect earlier 0.1.x releases, so update to 0.1.13.
npm install path-to-regexp@0.1.13Fixed within 0.1.x, affecting earlier releases
path-to-regexp vulnerable to Regular Expression Denial of Service via multiple route parameters
- Affected
- <0.1.13
- Fixed in
- 0.1.13
path-to-regexp contains a ReDoS
- Affected
- <0.1.12
- Fixed in
- 0.1.12
path-to-regexp outputs backtracking regular expressions
- Affected
- >=0.2.0 <1.9.0 · <0.1.10 · >=7.0.0 <8.0.0 · >=2.0.0 <3.3.0 · >=4.0.0 <6.3.0
- Fixed in
- 0.1.10, 1.9.0, 3.3.0, 6.3.0, 8.0.0
Which of your client projects are still on path-to-regexp 0.1?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact path-to-regexp version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other path-to-regexp versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the npm registry. Refreshed daily.