Is minimatch 8.0 vulnerable?
npm · 8 releases from 8.0.0 to 8.0.7 · latest minimatch is 11.0.3 · checked 2 Nov 2026
Yes: 1 known advisory
Yes. minimatch 8.0.7, the last 8.0 release, is affected by 1 known security advisory (1 medium), including CVE-2026-118764. 3 more affect earlier 8.0.x releases. Upgrade to 11.0.1 or later to fix all of them.
npm install minimatch@11.0.1Advisories affecting minimatch 8.0.7
minimatch has potential denial of service via globparts amplification
- Affected
- <11.0.1
- Fixed in
- 11.0.1
Fixed within 8.0.x, affecting earlier releases
minimatch has ReDoS: matchOne() combinatorial backtracking via multiple non-adjacent GLOBSTAR segments
- Affected
- >=10.0.0 <10.2.3 · >=9.0.0 <9.0.7 · >=8.0.0 <8.0.6 · >=7.0.0 <7.4.8 · >=6.0.0 <6.2.2 · >=5.0.0 <5.1.8 · >=4.0.0 <4.2.5 · <3.1.3
- Fixed in
- 3.1.3, 4.2.5, 5.1.8, 6.2.2, 7.4.8, 8.0.6, 9.0.7, 10.2.3
minimatch ReDoS: nested *() extglobs generate catastrophically backtracking regular expressions
- Affected
- >=10.0.0 <10.2.3 · >=9.0.0 <9.0.7 · >=8.0.0 <8.0.6 · >=7.0.0 <7.4.8 · >=6.0.0 <6.2.2 · >=5.0.0 <5.1.8 · >=4.0.0 <4.2.5 · <3.1.4
- Fixed in
- 3.1.4, 4.2.5, 5.1.8, 6.2.2, 7.4.8, 8.0.6, 9.0.7, 10.2.3
minimatch has a ReDoS via repeated wildcards with non-matching literal in pattern
- Affected
- >=10.0.0 <10.2.1 · >=9.0.0 <9.0.6 · >=8.0.0 <8.0.5 · >=7.0.0 <7.4.7 · >=6.0.0 <6.2.1 · >=5.0.0 <5.1.7 · >=4.0.0 <4.2.4 · <3.1.3
- Fixed in
- 3.1.3, 4.2.4, 5.1.7, 6.2.1, 7.4.7, 8.0.5, 9.0.6, 10.2.1
Which of your client projects are still on minimatch 8.0?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact minimatch version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other minimatch versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the npm registry. Refreshed daily.