CVE-2026-4923: path-to-regexp vulnerable to Regular Expression Denial of Service via multiple wildcards

Published Mar 26, 2026
·
Updated

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.

Other sources

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 you are using multiple wildcard parameters, you can check the regex output with a tool such as

IBM

Affected Software

4 affected componentsFixes available
npm/path-to-regexp<8.4.0
npm/path-to-regexp>=8.0.0<8.4.0
8.4.0
pillarjs Path-to-regexp Node.js>=8.0.0<8.4.0
IBM watsonx.data intelligence<=5.2.2, 5.3.0, 5.3.1, 5.3.1-patch-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/path-to-regexp to a version that resolves this vulnerability.

    Fixed in 8.4.0
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 8.4.0

Event History

Mar 26, 2026
CVE Published
via MITRE·07:02 PM
Data Sourced
via MITRE·07:02 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:17 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:17 PM
Affected Software
Mar 27, 2026
Advisory Published
via GitHub·10:23 PM
Data Sourced
via GitHub·10:23 PM
DescriptionSeverityWeaknessAffected Software
Jun 24, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-4923?

CVE-2026-4923 has a medium severity rating due to its potential for Regular Expression Denial of Service (ReDoS) when multiple wildcards are used.

2

How do I fix CVE-2026-4923?

To fix CVE-2026-4923, update the path-to-regexp package to version 8.4.0 or later.

3

What software is affected by CVE-2026-4923?

CVE-2026-4923 affects the path-to-regexp package versions below 8.4.0.

4

Can CVE-2026-4923 be exploited in production environments?

Yes, CVE-2026-4923 can be exploited in production environments, potentially leading to service outages.

5

What is the cause of CVE-2026-4923?

CVE-2026-4923 is caused by the use of multiple wildcards in regular expressions, leading to excessive backtracking.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203