CVE-2026-4867: path-to-regexp, отказ на услуга

Описание

Оригинално описание

Impact: A bad regular expression is generated any time you have three or more parameters within a single segment, separated by something that is not a period (.). For example, /:a-:b-:c or /:a-:b-:c-:d. The backtrack protection added in [email protected] only prevents ambiguity for two parameters. With three or more, the generated lookahead does not block single separator characters, so capture groups overlap and cause catastrophic backtracking. Patches: Upgrade to [email protected] Custom regex patterns in route definitions (e.g., /:a-:b([^-/]+)-:c([^-/]+)) are not affected because they override the default capture group. 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-:c to /:a-:b([^-/]+)-:c([^-/]+). If paths cannot be rewritten and versions cannot be upgraded, another alternative is to limit the URL length.

Засегнати продукти

• path-to-regexp path-to-regexp: преди 0.1.13

Вид слабост

• CWE-1333 Inefficient Regular Expression Complexity

История

Други уязвимости в path-to-regexp path-to-regexp

• 5.9CVE-2026-4923
• 7.5CVE-2026-4926

Първоизточници

• https://www.cve.org/CVERecord?id=CVE-2026-4867
• https://nvd.nist.gov/vuln/detail/CVE-2026-4867
• https://github.com/advisories/GHSA-9wv6-86v2-598j
• https://blakeembrey.com/posts/2024-09-web-redos
• https://cna.openjsf.org/security-advisories.html