path-to-regexp vulnerabilities
Express style path to RegExp utility
- Registry
- npm
- Latest
- 9.0.0
- License
- MIT
5 known advisories
The latest version, 9.0.0, is not affected by any of them. Projects on older versions may be.
npm install path-to-regexp@9.0.0Security advisories for path-to-regexp
path-to-regexp vulnerable to Regular Expression Denial of Service via multiple wildcards
- Affected
- >=8.0.0 <8.4.0
- Fixed in
- 8.4.0
path-to-regexp vulnerable to Denial of Service via sequential optional groups
- Affected
- >=8.0.0 <8.4.0
- Fixed in
- 8.4.0
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 still run an old path-to-regexp?
NPMscan reads the package-lock.json, yarn.lock and pnpm-lock.yaml in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other npm packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the npm registry.