minimatch: potential denial of service via globparts amplification
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 11.0.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The minimatch JavaScript library, a utility that converts glob patterns into regular expressions, is affected when it processes certain glob patterns at higher optimization levels. A specially crafted, short glob pattern can cause excessive CPU and memory use during compilation, which could make an application unresponsive.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
minimatch is a minimal matching utility for converting glob expressions into JavaScript RegExp objects. Prior to 11.0.1, src/index.ts implements firstPhasePreProcess() so that, at optimizationLevel 2 or higher, it repeatedly expands attacker-controlled **/.. pattern segments inside a fixpoint loop, allowing generated globParts entries to be processed and expanded again. secondPhasePreProcess() then compares the expanded entries pairwise, so a short malicious glob can cause excessive CPU and memory consumption during pattern compilation. This issue is fixed in version 11.0.1.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- isaacs minimatch
fixed in 11.0.1
References 3
GitHub · isaacs/minimatch
Questions about CVE-2026-118764
What does this mean?
An attacker who can supply a glob pattern can make minimatch use excessive CPU and memory while compiling that pattern, which denies service to the program using it.Source: github.com
Am I affected, and how do I check?
The advisory names minimatch 10.2.6 as affected, and the problem only occurs when optimizationLevel is 2 or higher. To check, run npm ls minimatch to see the installed version and look for optimizationLevel set to 2 or higher in the code that calls minimatch.Source: github.com
What should I do about it?
Upgrade minimatch to version 11.0.1 or later, which is the listed patched version.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data