GitHub Advisoryadvisory · npm

GHSA-27v5-c462-wpq7 path-to-regexp vulnerable to Regular Expression Denial of Service via multiple wildcards

MEDIUM Published 2026-03-27 Modified 2026-03-27 Official page ↗
Aliases
CVE-2026-4923
Ecosystem
npm
Packages
path-to-regexp
Severity
Moderate
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Weaknesses
CWE-1333
Reviewed
2026-03-27

Affected packages

• npm path-to-regexp: >= 8.0.0, < 8.4.0 → fixed in 8.4.0

Description

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.

Related

Alias · CVE (1)

  • CVE-2026-4923 Impact: When using multiple wildcards, combined with at least one parameter, a regular expression can be generated that is vulnerable to… vulnerability

Weakness · CWE (1)

  • CWE-1333 Inefficient Regular Expression Complexity weakness

References