minimatch vulnerabilities
a glob matcher in javascript
- Registry
- npm
- Latest
- 10.2.6
- License
- BlueOak-1.0.0
5 known advisories
The latest version, 10.2.6, is not affected by any of them. Projects on older versions may be.
npm install minimatch@10.2.6Security advisories for minimatch
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
minimatch ReDoS vulnerability
- Affected
- <3.0.5
- Fixed in
- 3.0.5
Regular Expression Denial of Service in minimatch
- Affected
- <3.0.2
- Fixed in
- 3.0.2
Which of your client projects still run an old minimatch?
NPMscan reads the package-lock.json, yarn.lock and pnpm-lock.yaml in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other npm packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the npm registry.