CVE-2026-4926: path-to-regexp vulnerable to Denial of Service via sequential optional groups

Published Mar 26, 2026
·
Updated

Impact

A bad regular expression is generated any time you have multiple sequential optional groups (curly brace syntax), such as {a}{b}{c}:z. The generated regex grows exponentially with the number of groups, causing denial of service.

Patches

Fixed in version 8.4.0.

Workarounds

Limit the number of sequential optional groups in route patterns. Avoid passing user-controlled input as route patterns.

Other sources

Impact:

A bad regular expression is generated any time you have multiple sequential optional groups (curly brace syntax), such as {a}{b}{c}:z. The generated regex grows exponentially with the number of groups, causing denial of service.

Patches:

Fixed in version 8.4.0.

Workarounds:

Limit the number of sequential optional groups in route patterns. Avoid passing user-controlled input as route patterns.

MITRE

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 path-to-regexp to a version that resolves this vulnerability.

    Fixed in 8.4.0
  3. Configuration

    Avoid generating route patterns that contain multiple sequential optional groups (curly brace syntax), such as `{a}{b}{c}:z`; instead limit the number of sequential optional groups in route patterns to prevent denial of service.

    route pattern handling sequential optional groups in route patterns = Limit the number of sequential optional groups
  4. Configuration

    Avoid passing user-controlled input as route patterns.

    route pattern handling route pattern input source = Do not pass user-controlled input as route patterns

Event History

Mar 26, 2026
CVE Published
via MITRE·06:59 PM
Data Sourced
via MITRE·06:59 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:17 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:17 PM
Affected Software
Data Sourced
via Red Hat·08:03 PM
DescriptionSeverityAffected 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-4926?

CVE-2026-4926 has a high severity due to its potential to cause Denial of Service through poorly formed regular expressions.

2

How do I fix CVE-2026-4926?

To fix CVE-2026-4926, upgrade the path-to-regexp library to version 8.4.0 or later.

3

What versions of path-to-regexp are affected by CVE-2026-4926?

Versions of path-to-regexp from 8.0.0 up to but not including 8.4.0 are affected by CVE-2026-4926.

4

What impact does CVE-2026-4926 have on applications?

CVE-2026-4926 can lead to CPU exhaustion in applications using vulnerable versions, resulting in Denial of Service.

5

What type of vulnerability is CVE-2026-4926?

CVE-2026-4926 is a vulnerability related to Denial of Service caused by inefficient regex processing.

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