CVE-2026-26996: minimatch has a ReDoS via repeated wildcards with non-matching literal in pattern

Published Feb 18, 2026
·
Updated

Summary minimatch is vulnerable to Regular Expression Denial of Service (ReDoS) when a glob pattern contains many consecutive wildcards followed by a literal character that doesn't appear in the test string. Each compiles to a separate [^/]? regex group, and when the match fails, V8's regex engine backtracks exponentially across all possible splits.

The time complexity is O(4^N) where N is the number of characters. With N=15, a single minimatch() call takes ~2 seconds. With N=34, it hangs effectively forever.

Details Give all details on the vulnerability. Pointing to the incriminated source code is very helpful for the maintainer.

PoC When minimatch compiles a glob pattern, each becomes [^/]? in the generated regex. For a pattern like X:

/^(?!\.)[^/]?[^/]?[^/]?[^/]?[^/]?[^/]?[^/]?[^/]?[^/]?[^/]?[^/]?[^/]?[^/]?[^/]?[^/]?X[^/]?[^/]?[^/]?$/

When the test string doesn't contain X, the regex engine must try every possible way to distribute the characters across all the [^/]? groups before concluding no match exists. With N groups and M characters, this is O(C(N+M, N)) — exponential. Impact Any application that passes user-controlled strings to minimatch() as the pattern argument is vulnerable to DoS. This includes: - File search/filter UIs that accept glob patterns - .gitignore-style filtering with user-defined rules - Build tools that accept glob configuration - Any API that exposes glob matching to untrusted input

Other sources

minimatch is a minimal matching utility for converting glob expressions into JavaScript RegExp objects. Versions 10.2.0 and below are vulnerable to Regular Expression Denial of Service (ReDoS) when a glob pattern contains many consecutive wildcards followed by a literal character that doesn't appear in the test string. Each compiles to a separate [^/]? regex group, and when the match fails, V8's regex engine backtracks exponentially across all possible splits. The time complexity is O(4^N) where N is the number of characters. With N=15, a single minimatch() call takes ~2 seconds. With N=34, it hangs effectively forever. Any application that passes user-controlled strings to minimatch() as the pattern argument is vulnerable to DoS. This issue has been fixed in version 10.2.1.

NVD

Affected Software

19 affected componentsFixes available
npm/minimatch<10.2.1
10.2.1
Minimatch Project Minimatch Node.js<10.2.1
npm/minimatch<3.1.3
3.1.3
npm/minimatch>=4.0.0<4.2.4
4.2.4
npm/minimatch>=5.0.0<5.1.7
5.1.7
npm/minimatch>=6.0.0<6.2.1
6.2.1
npm/minimatch>=7.0.0<7.4.7
7.4.7
npm/minimatch>=8.0.0<8.0.5
8.0.5
npm/minimatch>=9.0.0<9.0.6
9.0.6
npm/minimatch>=10.0.0<10.2.1
10.2.1
Minimatch Project Minimatch Node.js>=3.0.0<3.1.3
Minimatch Project Minimatch Node.js>=4.0.0<4.2.4
Minimatch Project Minimatch Node.js>=5.0.0<5.1.7
Minimatch Project Minimatch Node.js>=6.0.0<6.2.1
Minimatch Project Minimatch Node.js>=7.0.0<7.4.7
Minimatch Project Minimatch Node.js>=8.0.0<8.0.5
Minimatch Project Minimatch Node.js>=9.0.0<9.0.6
Minimatch Project Minimatch Node.js>=10.0.0<10.2.1
IBM API Connect V12 OnPrem<=All

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/minimatch to a version that resolves this vulnerability.

    Fixed in 10.2.1
  2. Upgrade

    Upgrade npm/minimatch to a version that resolves this vulnerability.

    Fixed in 3.1.3
  3. Upgrade

    Upgrade npm/minimatch to a version that resolves this vulnerability.

    Fixed in 4.2.4
  4. Upgrade

    Upgrade npm/minimatch to a version that resolves this vulnerability.

    Fixed in 5.1.7
  5. Upgrade

    Upgrade npm/minimatch to a version that resolves this vulnerability.

    Fixed in 6.2.1
  6. Upgrade

    Upgrade npm/minimatch to a version that resolves this vulnerability.

    Fixed in 7.4.7
  7. Upgrade

    Upgrade npm/minimatch to a version that resolves this vulnerability.

    Fixed in 8.0.5
  8. Upgrade

    Upgrade npm/minimatch to a version that resolves this vulnerability.

    Fixed in 9.0.6
  9. Upgrade

    Upgrade minimatch to a version that resolves this vulnerability.

    Fixed in 10.2.1

Event History

Feb 18, 2026
Advisory Published
via GitHub·10:38 PM
Data Sourced
via GitHub·10:38 PM
DescriptionWeaknessAffected Software
Feb 20, 2026
CVE Published
via MITRE·03:05 AM
Data Sourced
via MITRE·03:05 AM
DescriptionWeakness
Data Sourced
via NVD·03:16 AM
RemedyDescriptionSeverityWeaknessAffected Software
Data Sourced
via Red Hat·04:01 AM
DescriptionSeverityAffected Software
Jul 7, 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-26996?

CVE-2026-26996 is classified as a Regular Expression Denial of Service (ReDoS) vulnerability.

2

How do I fix CVE-2026-26996?

To fix CVE-2026-26996, upgrade the minimatch package to version 10.2.1 or later.

3

What versions of minimatch are affected by CVE-2026-26996?

CVE-2026-26996 affects versions of minimatch prior to 10.2.1.

4

What pattern causes the vulnerability in CVE-2026-26996?

CVE-2026-26996 is triggered by glob patterns that contain many consecutive '*' wildcards followed by a non-matching literal character.

5

Is CVE-2026-26996 specific to a particular programming language?

CVE-2026-26996 specifically affects the minimatch package used within Node.js applications.

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