Advisory

GHSA-37ch-88jc-xwx2

Also known as: CVE-2024-45296, CVE-2026-4867, GHSA-9wv6-86v2-598j

Summary

path-to-regexp vulnerable to Regular Expression Denial of Service via multiple route parameters

Details

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.

References

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-03-27 20:04 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

path-to-regexp

npm · All systems

Affected

  • introduced 0, fixed 0.1.13 (semver)

Fixed versions

0.1.13

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences