path-to-regexp
Affected
- introduced
8.0.0, fixed8.4.0(semver)
Fixed versions
8.4.0
Fix
- Fixed version
8.4.0npm install [email protected]
Advisory
Also known as: CVE-2026-4923
path-to-regexp vulnerable to Regular Expression Denial of Service via multiple wildcards
Impact
When using multiple wildcards, combined with at least one parameter, a regular expression can be generated that is vulnerable to ReDoS. This backtracking vulnerability requires the second wildcard to be somewhere other than the end of the path.
Unsafe examples:
/*foo-*bar-:baz
/*a-:b-*c-:d
/x/*a-:b/*c/y
Safe examples:
/*foo-:bar
/*foo-:bar-*baz
Patches
Upgrade to version 8.4.0.
Workarounds
If developers are using multiple wildcard parameters, they can check the regex output with a tool such as https://makenowjust-labs.github.io/recheck/playground/ to confirm whether a path is vulnerable.
Medium Basis: The source's own band: MODERATE
8.0.0, fixed 8.4.0 (semver)8.4.0
8.4.0npm install [email protected]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
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0