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

High

OSV id
GHSA-3ppc-4f35-3m26
Also known as
CVE-2026-26996
Published
Last modified

Affected packages

PackageAffected versionsFixed in
minimatch
npm
>= 10.0.0, < 10.2.1 10.2.1
minimatch
npm
>= 9.0.0, < 9.0.6 9.0.6
minimatch
npm
>= 8.0.0, < 8.0.5 8.0.5
minimatch
npm
>= 7.0.0, < 7.4.7 7.4.7
minimatch
npm
>= 6.0.0, < 6.2.1 6.2.1
minimatch
npm
>= 5.0.0, < 5.1.7 5.1.7
minimatch
npm
>= 4.0.0, < 4.2.4 4.2.4
minimatch
npm
< 3.1.3 3.1.3

Versions we track that it affects: minimatch 9.0.4; minimatch 9.0.4; minimatch 9.0.4; minimatch 9.0.4; minimatch 9.0.4; minimatch 9.0.4; minimatch 9.0.4; minimatch 9.0.4

How to fix it

minimatch (npm)

Upgrade minimatch to 10.2.1 or later.

npm install minimatch@10.2.1
# if it is an indirect dependency: npm update minimatch (or npm audit fix)
  • If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

minimatch (npm)

Upgrade minimatch to 9.0.6 or later.

npm install minimatch@9.0.6
# if it is an indirect dependency: npm update minimatch (or npm audit fix)
  • If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

minimatch (npm)

Upgrade minimatch to 8.0.5 or later.

npm install minimatch@8.0.5
# if it is an indirect dependency: npm update minimatch (or npm audit fix)
  • If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

minimatch (npm)

Upgrade minimatch to 7.4.7 or later.

npm install minimatch@7.4.7
# if it is an indirect dependency: npm update minimatch (or npm audit fix)
  • If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

minimatch (npm)

Upgrade minimatch to 6.2.1 or later.

npm install minimatch@6.2.1
# if it is an indirect dependency: npm update minimatch (or npm audit fix)
  • If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

minimatch (npm)

Upgrade minimatch to 5.1.7 or later.

npm install minimatch@5.1.7
# if it is an indirect dependency: npm update minimatch (or npm audit fix)
  • If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

minimatch (npm)

Upgrade minimatch to 4.2.4 or later.

npm install minimatch@4.2.4
# if it is an indirect dependency: npm update minimatch (or npm audit fix)
  • If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

minimatch (npm)

Upgrade minimatch to 3.1.3 or later.

npm install minimatch@3.1.3
# if it is an indirect dependency: npm update minimatch (or npm audit fix)
  • If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

Not sure whether your project uses an affected version? Check your lockfile below for free.

Details

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.

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: GitHub Advisory Database via OSV.dev (CC-BY 4.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.