path-to-regexp vulnerable to Regular Expression Denial of Service via multiple route parameters
Résumé
path-to-regexp vulnerable to Regular Expression Denial of Service via multiple route parameters
Description d'origine
La description telle que publiée par la source (souvent en anglais).
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 path-to-regexp@0.1.12 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 path-to-regexp@0.1.13
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.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
État des correctifs par distribution
Paquets corrigés publiés par chaque distribution pour cette CVE
- Debian DEBIAN-CVE-2026-4867 node-path-to-regexp Corrigé dans: 1.0.1-1
- Ubuntu UBUNTU-CVE-2026-4867 node-path-to-regexp
Références
- advisory cna.openjsf.org
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- web blakeembrey.com