CVE-2026-26996: minimatch has a ReDoS via repeated wildcards with non-matching literal in pattern
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
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/minimatchto a version that resolves this vulnerability.Fixed in 10.2.1 - Upgrade
Upgrade
npm/minimatchto a version that resolves this vulnerability.Fixed in 3.1.3 - Upgrade
Upgrade
npm/minimatchto a version that resolves this vulnerability.Fixed in 4.2.4 - Upgrade
Upgrade
npm/minimatchto a version that resolves this vulnerability.Fixed in 5.1.7 - Upgrade
Upgrade
npm/minimatchto a version that resolves this vulnerability.Fixed in 6.2.1 - Upgrade
Upgrade
npm/minimatchto a version that resolves this vulnerability.Fixed in 7.4.7 - Upgrade
Upgrade
npm/minimatchto a version that resolves this vulnerability.Fixed in 8.0.5 - Upgrade
Upgrade
npm/minimatchto a version that resolves this vulnerability.Fixed in 9.0.6 - Upgrade
Upgrade
minimatchto a version that resolves this vulnerability.Fixed in 10.2.1
Event History
Frequently Asked Questions
What is the severity of CVE-2026-26996?
CVE-2026-26996 is classified as a Regular Expression Denial of Service (ReDoS) vulnerability.
How do I fix CVE-2026-26996?
To fix CVE-2026-26996, upgrade the minimatch package to version 10.2.1 or later.
What versions of minimatch are affected by CVE-2026-26996?
CVE-2026-26996 affects versions of minimatch prior to 10.2.1.
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.
Is CVE-2026-26996 specific to a particular programming language?
CVE-2026-26996 specifically affects the minimatch package used within Node.js applications.