CVE-2026-4867
Impact: A bad regular expression is generated any time you have …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- blakeembrey.com/posts/2024-09-web-redos
- cna.openjsf.org/security-advisories.html
- github.com/advisories/GHSA-9wv6-86v2-598j
- github.com/pillarjs/path-to-regexp/security/advisories/GHSA-37ch-88jc-xwx2
- nvd.nist.gov/vuln/detail/CVE-2026-4867
- github.com/pillarjs/path-to-regexp/releases/tag/v.0.1.13
- github.com/advisories/GHSA-37ch-88jc-xwx2
- nvd.nist.gov/vuln/detail/CVE-2026-4867
- cve.org/CVERecord?id=CVE-2026-4867
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.