CVE-2026-4867
CVE-2026-4867 · path-to-regexp vulnerable to Regular Expression Denial of Service via multiple route parameters
Cette page présente des faits issus de sources publiques. Consultez l’avis original avant toute mise à jour.
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.
CVSS 7.5 · Élevée · EPSS 0,5% · Correctif disponible
- Publication
- Mise à jour
Pile logicielle: system
Produits et versions concernés
path-to-regexp
- Versions du logiciel
- ≥ 0, < 0.1.13: Concernée (semver)
Mettez à jour vers 0.1.13
node-path-to-regexp Debian:12
- Plages de versions concernées
- ECOSYSTEM: < 1.0.1-1
Mettez à jour vers 1.0.1-1
node-path-to-regexp Debian:13
- Plages de versions concernées
- ECOSYSTEM: < 1.0.1-1
Mettez à jour vers 1.0.1-1
node-path-to-regexp Debian:14
- Plages de versions concernées
- ECOSYSTEM: < 1.0.1-1
Mettez à jour vers 1.0.1-1