CVE-2024-45296: path-to-regexp outputs backtracking regular expressions
Impact A bad regular expression is generated any time you have two parameters within a single segment, separated by something that is not a period (.). For example, /:a-:b. Patches For users of 0.1, upgrade to 0.1.10. All other users should upgrade to 8.0.0.
Published Sep 9, 2024 · Updated Jan 24, 2025
Affected packages
path-to-regexp
- Ecosystem
- npm
- Affected
- < 0.1.10
- Fixed in
- 0.1.10
- Check
npm ls path-to-regexp
path-to-regexp
- Ecosystem
- npm
- Affected
- >= 0.2.0, < 1.9.0
- Fixed in
- 1.9.0
- Check
npm ls path-to-regexp
path-to-regexp
- Ecosystem
- npm
- Affected
- >= 2.0.0, < 3.3.0
- Fixed in
- 3.3.0
- Check
npm ls path-to-regexp
path-to-regexp
- Ecosystem
- npm
- Affected
- >= 7.0.0, < 8.0.0
- Fixed in
- 8.0.0
- Check
npm ls path-to-regexp
path-to-regexp
- Ecosystem
- npm
- Affected
- >= 4.0.0, < 6.3.0
- Fixed in
- 6.3.0
- Check
npm ls path-to-regexp
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
A bad regular expression is generated any time you have two parameters within a single segment, separated by something that is not a period (.). For example, /:a-:b.
Patches
For users of 0.1, upgrade to 0.1.10. All other users should upgrade to 8.0.0.
These versions add backtrack protection when a custom regex pattern is not provided:
They do not protect against vulnerable user supplied capture groups. Protecting against explicit user patterns is out of scope for old versions and not considered a vulnerability.
Version 7.1.0 can enable strict: true and get an error when the regular expression might be bad.
Version 8.0.0 removes the features that can cause a ReDoS.
Workarounds
All versions can be patched by providing a custom regular expression for parameters after the first in a single segment. As long as the custom regular expression does not match the text before the parameter, you will be safe. For example, change /:a-:b to /:a-:b([^-/]+).
If paths cannot be rewritten and versions cannot be upgraded, another alternative is to limit the URL length. For example, halving the attack string improves performance by 4x faster.
Details
Using /:a-:b will produce the regular expression /^\/([^\/]+?)-([^\/]+?)\/?$/. This can be exploited by a path such as /a${'-a'.repeat(8_000)}/a. OWASP has a good example of why this occurs, but the TL;DR is the /a at the end ensures this route would never match but due to naive backtracking it will still attempt every combination of the :a-:b on the repeated 8,000 -a.
Because JavaScript is single threaded and regex matching runs on the main thread, poor performance will block the event loop and can lead to a DoS. In local benchmarks, exploiting the unsafe regex will result in performance that is over 1000x worse than the safe regex. In a more realistic environment using Express v4 and 10 concurrent connections, this translated to average latency of ~600ms vs 1ms.
References
Credited to blakeembrey, ctcpip, uniabis, stbenjam, pseudoralph, mschfh, jusemon, panva, alenovik, jaydeep-bypt.
References
- https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-9wv6-86v2-598j
- https://github.com/pillarjs/path-to-regexp/commit/29b96b4a1de52824e1ca0f49a701183cc4ed476f
- https://github.com/pillarjs/path-to-regexp/commit/60f2121e9b66b7b622cc01080df0aabda9eedee6
- https://nvd.nist.gov/vuln/detail/CVE-2024-45296
- https://github.com/pillarjs/path-to-regexp/commit/925ac8e3c5780b02f58cbd4e52f95da8ad2ac485
- https://github.com/pillarjs/path-to-regexp/commit/d31670ae8f6e69cbfd56e835742195b7d10942ef
- https://github.com/pillarjs/path-to-regexp/commit/f1253b47b347dcb909e3e80b0eb2649109e59894
- https://github.com/pillarjs/path-to-regexp/releases/tag/v6.3.0
- https://security.netapp.com/advisory/ntap-20250124-0001
- https://github.com/advisories/GHSA-9wv6-86v2-598j
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-4867
path-to-regexp vulnerable to Regular Expression Denial of Service via multiple route parameters
high7.5Mar 27, 2026CVE-2026-4923
path-to-regexp vulnerable to Regular Expression Denial of Service via multiple wildcards
medium5.9Mar 27, 2026CVE-2026-4926
path-to-regexp vulnerable to Denial of Service via sequential optional groups
high7.5Mar 27, 2026CVE-2024-52798
path-to-regexp contains a ReDoS
high7.5Dec 5, 2024
