CVE-2026-4923: path-to-regexp vulnerable to Regular Expression Denial of Service via multiple wildcards
Impact When using multiple wildcards, combined with at least one parameter, a regular expression can be generated that is vulnerable to ReDoS. This backtracking vulnerability requires the second wildcard to be somewhere other than the end of the path. Unsafe examples: Safe examples: Patches Upgrade to version 8.4.0.
Published Mar 27, 2026
Affected packages
path-to-regexp
- Ecosystem
- npm
- Affected
- >= 8.0.0, < 8.4.0
- Fixed in
- 8.4.0
- Check
npm ls path-to-regexp
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
When using multiple wildcards, combined with at least one parameter, a regular expression can be generated that is vulnerable to ReDoS. This backtracking vulnerability requires the second wildcard to be somewhere other than the end of the path.
Unsafe examples:
/*foo-*bar-:baz
/*a-:b-*c-:d
/x/*a-:b/*c/ySafe examples:
/*foo-:bar
/*foo-:bar-*bazPatches
Upgrade to version 8.4.0.
Workarounds
If developers are using multiple wildcard parameters, they can check the regex output with a tool such as https://makenowjust-labs.github.io/recheck/playground/ to confirm whether a path is vulnerable.
Credited to blakeembrey, UlisesGascon.
References
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-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, 2024CVE-2024-45296
path-to-regexp outputs backtracking regular expressions
high7.5Sep 9, 2024
