Skip to content

Update dependency minimatch to v10.2.1 [SECURITY] - autoclosed#1627

Closed
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm-minimatch-vulnerability
Closed

Update dependency minimatch to v10.2.1 [SECURITY] - autoclosed#1627
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm-minimatch-vulnerability

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 23, 2026

This PR contains the following updates:

Package Change Age Confidence
minimatch 10.1.110.2.1 age confidence

GitHub Vulnerability Alerts

CVE-2026-26996

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

Thanks to @​ljharb for back-porting the fix to legacy versions of minimatch.


Release Notes

isaacs/minimatch (minimatch)

v10.2.1

Compare Source

v10.2.0

Compare Source

v10.1.3

Compare Source

v10.1.2

Compare Source


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title Update dependency minimatch to v10.2.1 [SECURITY] Update dependency minimatch to v10.2.1 [SECURITY] - autoclosed Feb 23, 2026
@renovate renovate bot closed this Feb 23, 2026
@renovate renovate bot deleted the renovate/npm-minimatch-vulnerability branch February 23, 2026 14:51
@renovate renovate bot changed the title Update dependency minimatch to v10.2.1 [SECURITY] - autoclosed Update dependency minimatch to v10.2.1 [SECURITY] Feb 25, 2026
@renovate renovate bot reopened this Feb 25, 2026
@renovate renovate bot force-pushed the renovate/npm-minimatch-vulnerability branch 2 times, most recently from 466cf59 to edd2a05 Compare February 25, 2026 02:48
@renovate renovate bot changed the title Update dependency minimatch to v10.2.1 [SECURITY] Update dependency minimatch to v10.2.1 [SECURITY] - autoclosed Feb 25, 2026
@renovate renovate bot closed this Feb 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

0 participants