Skip to content

Update dependency minimatch to v3.1.3 [SECURITY]#37

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/npm-minimatch-vulnerability
Open

Update dependency minimatch to v3.1.3 [SECURITY]#37
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/npm-minimatch-vulnerability

Conversation

@renovate
Copy link

@renovate renovate bot commented Nov 20, 2022

This PR contains the following updates:

Package Change Age Confidence
minimatch 3.0.43.1.3 age confidence

GitHub Vulnerability Alerts

CVE-2022-3517

A vulnerability was found in the minimatch package. This flaw allows a Regular Expression Denial of Service (ReDoS) when calling the braceExpand function with specific arguments, resulting in a Denial of Service.

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)

v3.1.3

Compare Source

v3.1.2

Compare Source

v3.1.1

Compare Source

v3.1.0

Compare Source

v3.0.8

Compare Source

v3.0.7

Compare Source

v3.0.6

Compare Source

v3.0.5

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 force-pushed the renovate/npm-minimatch-vulnerability branch from b6e7b94 to 0d227e0 Compare February 22, 2026 17:15
@renovate renovate bot changed the title Update dependency minimatch to v3.0.5 [SECURITY] Update dependency minimatch to v10 [SECURITY] Feb 22, 2026
@renovate renovate bot force-pushed the renovate/npm-minimatch-vulnerability branch from 0d227e0 to 2ca6524 Compare February 24, 2026 23:48
@renovate renovate bot changed the title Update dependency minimatch to v10 [SECURITY] Update dependency minimatch to v3.0.5 [SECURITY] Feb 24, 2026
@renovate renovate bot force-pushed the renovate/npm-minimatch-vulnerability branch from 2ca6524 to eb71ce1 Compare February 26, 2026 18:05
@renovate renovate bot changed the title Update dependency minimatch to v3.0.5 [SECURITY] Update dependency minimatch to v3.1.3 [SECURITY] Feb 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants