CVE-2026-4926: path-to-regexp vulnerable to Denial of Service via sequential optional groups
Impact A bad regular expression is generated any time you have multiple sequential optional groups (curly brace syntax), such as {a}{b}{c}:z. The generated regex grows exponentially with the number of groups, causing denial of service. Patches Fixed in version 8.4.0. Workarounds Limit the number of sequential optional groups in route patterns. Avoid passing user-controlled input as route patterns.
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
A bad regular expression is generated any time you have multiple sequential optional groups (curly brace syntax), such as {a}{b}{c}:z. The generated regex grows exponentially with the number of groups, causing denial of service.
Patches
Fixed in version 8.4.0.
Workarounds
Limit the number of sequential optional groups in route patterns. Avoid passing user-controlled input as route patterns.
Credited to uug4na, 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-4923
path-to-regexp vulnerable to Regular Expression Denial of Service via multiple wildcards
medium5.9Mar 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
