VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

minimatch: vulnerability history, versions and safety

minimatch is a package in the npm ecosystem. Vulert records 5 vulnerabilities for it across 116 releases, from Oct 2018 to Feb 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded H5
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 26 Feb 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all minimatch vulnerabilities

Vulert verdict on minimatch 10.2.6 i

Updated on 23 Oct 2026

Good news: 10.2.6, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 5.

Package health score 78/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Quiet

What to do: Stay on 10.2.6 or newer. This can change: a vulnerability disclosed tomorrow can affect 10.2.6 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 10.2.6 — unaffected i
  • Vulnerabilities on record 5 over 7 years · 3 in the last year i
  • Latest disclosure 26 Feb 2026 i
  • Highest CVSS 8.7 i
  • With no published fix 0 i
  • Depended on by 99,955 packages i
  • Stars 3,526 i
  • OpenSSF scorecard 4/10 i
  • Last release 2 months ago i
  • Licence BlueOak-1.0.0 i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for minimatch, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
10.2.6 27 Jul 2026 none BlueOak-1.0.0 — Details →
10.2.5 30 Mar 2026 none BlueOak-1.0.0 — Details →
9.0.9 26 Feb 2026 H1 ISC Yes Details →
3.1.5 25 Feb 2026 H1 ISC Yes Details →
4.2.6 25 Feb 2026 H1 ISC Yes Details →
5.1.9 25 Feb 2026 H1 ISC Yes Details →
6.2.3 25 Feb 2026 H1 ISC Yes Details →
7.4.9 25 Feb 2026 H1 ISC Yes Details →
8.0.7 25 Feb 2026 H1 ISC Yes Details →
9.0.8 25 Feb 2026 H1 ISC Yes Details →
10.2.4 25 Feb 2026 none BlueOak-1.0.0 — Details →
3.1.4 25 Feb 2026 H1 ISC Yes Details →
4.2.5 25 Feb 2026 H1 ISC Yes Details →
5.1.8 25 Feb 2026 H1 ISC Yes Details →
6.2.2 25 Feb 2026 H1 ISC Yes Details →
7.4.8 25 Feb 2026 H1 ISC Yes Details →
8.0.6 25 Feb 2026 H1 ISC Yes Details →
9.0.7 25 Feb 2026 H1 ISC Yes Details →
10.2.3 25 Feb 2026 none BlueOak-1.0.0 — Details →
3.1.3 22 Feb 2026 H1 ISC Yes Details →
4.2.4 22 Feb 2026 H1 ISC Yes Details →
5.1.7 22 Feb 2026 H1 ISC Yes Details →
6.2.1 22 Feb 2026 H1 ISC Yes Details →
7.4.7 22 Feb 2026 H1 ISC Yes Details →
8.0.5 22 Feb 2026 H1 ISC Yes Details →
9.0.6 22 Feb 2026 H1 ISC Yes Details →
10.2.2 19 Feb 2026 H2 BlueOak-1.0.0 Yes Details →
10.2.1 17 Feb 2026 H2 BlueOak-1.0.0 Yes Details →
10.2.0 12 Feb 2026 H3 BlueOak-1.0.0 Yes Details →
10.1.3 12 Feb 2026 H3 BlueOak-1.0.0 Yes Details →
10.1.2 03 Feb 2026 H3 BlueOak-1.0.0 Yes Details →
10.1.1 28 Oct 2025 H3 BlueOak-1.0.0 Yes Details →
10.1.0 28 Oct 2025 H3 BlueOak-1.0.0 Yes Details →
10.0.3 12 Jun 2025 H3 ISC Yes Details →
10.0.2 11 Jun 2025 H3 ISC Yes Details →
10.0.1 08 Jul 2024 H3 ISC Yes Details →
10.0.0 08 Jul 2024 H3 ISC Yes Details →
9.0.5 25 Jun 2024 H1 ISC Yes Details →
9.0.4 28 Mar 2024 H1 ISC Yes Details →
9.0.3 06 Jul 2023 H1 ISC Yes Details →
9.0.2 23 Jun 2023 H1 ISC Yes Details →
9.0.1 20 May 2023 H1 ISC Yes Details →
9.0.0 09 Apr 2023 H1 ISC Yes Details →
7.4.6 09 Apr 2023 H1 ISC Yes Details →
8.0.4 09 Apr 2023 H1 ISC Yes Details →
8.0.3 03 Apr 2023 H1 ISC Yes Details →
7.4.5 03 Apr 2023 H1 ISC Yes Details →
8.0.2 02 Apr 2023 H1 ISC Yes Details →
8.0.1 02 Apr 2023 H1 ISC Yes Details →
8.0.0 02 Apr 2023 H1 ISC Yes Details →
7.4.4 01 Apr 2023 H1 ISC Yes Details →
7.4.3 22 Mar 2023 H1 ISC Yes Details →
7.4.2 01 Mar 2023 H1 ISC Yes Details →
7.4.1 01 Mar 2023 H1 ISC Yes Details →
7.4.0 01 Mar 2023 H1 ISC Yes Details →
7.3.0 27 Feb 2023 H1 ISC Yes Details →
7.2.0 26 Feb 2023 H1 ISC Yes Details →
7.1.4 26 Feb 2023 H1 ISC Yes Details →
7.1.3 25 Feb 2023 H1 ISC Yes Details →
7.1.2 24 Feb 2023 H1 ISC Yes Details →
7.1.1 24 Feb 2023 H1 ISC Yes Details →
7.1.0 22 Feb 2023 H1 ISC Yes Details →
7.0.1 22 Feb 2023 H1 ISC Yes Details →
7.0.0 20 Feb 2023 H1 ISC Yes Details →
6.2.0 13 Feb 2023 H1 ISC Yes Details →
6.1.10 13 Feb 2023 H1 ISC Yes Details →
6.1.9 13 Feb 2023 H1 ISC Yes Details →
6.1.8 11 Feb 2023 H1 ISC Yes Details →
6.1.7 11 Feb 2023 H1 ISC Yes Details →
6.1.6 22 Jan 2023 H1 ISC Yes Details →
6.1.5 17 Jan 2023 H1 ISC Yes Details →
4.2.3 17 Jan 2023 H1 ISC Yes Details →
5.1.6 17 Jan 2023 H1 ISC Yes Details →
6.1.4 17 Jan 2023 H1 ISC Yes Details →
6.1.3 17 Jan 2023 H1 ISC Yes Details →
4.2.2 17 Jan 2023 H1 ISC Yes Details →
5.1.5 17 Jan 2023 H1 ISC Yes Details →
6.1.2 17 Jan 2023 H1 ISC Yes Details →
6.1.1 17 Jan 2023 H1 ISC Yes Details →
6.1.0 17 Jan 2023 H1 ISC Yes Details →
6.0.4 16 Jan 2023 H1 ISC Yes Details →
6.0.3 15 Jan 2023 H1 ISC Yes Details →
6.0.2 15 Jan 2023 H1 ISC Yes Details →
6.0.1 15 Jan 2023 H1 ISC Yes Details →
6.0.0 14 Jan 2023 H1 ISC Yes Details →
5.1.4 14 Jan 2023 H1 ISC Yes Details →
5.1.3 14 Jan 2023 H1 ISC Yes Details →
5.1.2 20 Dec 2022 H1 ISC Yes Details →
5.1.1 29 Nov 2022 H1 ISC Yes Details →
5.1.0 16 May 2022 H1 ISC Yes Details →
5.0.1 24 Feb 2022 H1 ISC Yes Details →
3.0.8 15 Feb 2022 H1 ISC Yes Details →
3.1.2 15 Feb 2022 H1 ISC Yes Details →
5.0.0 15 Feb 2022 H1 ISC Yes Details →
4.2.1 15 Feb 2022 H1 ISC Yes Details →
4.2.0 15 Feb 2022 H1 ISC Yes Details →
4.1.1 13 Feb 2022 H1 ISC Yes Details →
3.0.7 13 Feb 2022 H1 ISC Yes Details →
3.1.1 13 Feb 2022 H1 ISC Yes Details →
3.1.0 13 Feb 2022 H1 ISC Yes Details →
4.1.0 13 Feb 2022 H1 — Yes Details →
4.0.0 13 Feb 2022 H1 — Yes Details →
3.0.6 12 Feb 2022 H1 — Yes Details →
3.0.5 06 Feb 2022 H1 — Yes Details →
3.0.4 07 May 2017 H2 — Yes Details →
3.0.3 08 Aug 2016 H2 — Yes Details →
3.0.2 17 Jun 2016 H2 — Yes Details →
3.0.0 27 Sep 2015 H3 — Yes Details →
2.0.10 23 Jul 2015 H3 — Yes Details →
2.0.9 18 Jul 2015 H3 — Yes Details →
2.0.8 19 May 2015 H3 — Yes Details →
2.0.7 29 Apr 2015 H3 — Yes Details →
2.0.6 29 Apr 2015 H3 — Yes Details →
2.0.5 29 Apr 2015 H3 — Yes Details →
2.0.4 12 Mar 2015 H3 — Yes Details →
2.0.3 10 Mar 2015 H3 — Yes Details →
2.0.2 10 Mar 2015 H3 — Yes Details →
2.0.1 01 Dec 2014 H3 — Yes Details →
2.0.0 01 Dec 2014 H3 — Yes Details →
1.0.0 28 Jul 2014 H3 — Yes Details →

The newest 120 of 145 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1
  • 2022 1
  • 2026 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 3 of the 5 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for minimatch

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-26996: minimatch Regular Expression Denial of Service via Repeated Wildcards 8.7 high 10.2.1 18 Feb 2026
CVE-2016-10540: Regular Expression Denial of Service in minimatch 7.5 high 3.0.2 09 Oct 2018
CVE-2022-3517: minmatch ReDoS vulnerability 7.5 high 3.0.5 18 Oct 2022
CVE-2026-27904: minimatch Catastrophic Backtracking Vulnerability in Regular Expressions 7.5 high 10.2.3 26 Feb 2026
CVE-2026-27903: Minimatch Combinatorial Backtracking Vulnerability Leading to ReDoS 7.5 high 10.2.3 26 Feb 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About minimatch

Is minimatch safe to use?

Vulert records 5 vulnerabilities for minimatch in npm: 0 critical, 5 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is minimatch's Vulert package health score?

Vulert scores minimatch 78/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of minimatch affected?

No. 10.2.6, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of minimatch should I use?

10.2.6 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does minimatch have?

5 vulnerabilities are recorded for minimatch in the npm ecosystem: 0 critical, 5 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new minimatch vulnerabilities disclosed?

3 vulnerabilities were recorded for minimatch in the last 12 months, and the oldest entry in this database dates to 09 Oct 2018. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of minimatch are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor minimatch for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the minimatch version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.