CVE-2026-26996
Fix: isaacs/minimatch@2e111f3CVE-2026-26996 is a CWE-1333 vulnerability in minimatch. O3 Security confirms whether CVE-2026-26996 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
minimatch has a ReDoS via repeated wildcards with non-matching literal in pattern
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
minimatchnpmDescription
minimatch is a minimal matching utility for converting glob expressions into JavaScript RegExp objects. Versions 10.2.0 and below are 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. Any application that passes user-controlled strings to minimatch() as the pattern argument is vulnerable to DoS. This issue has been fixed in version 10.2.1.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | minimatch | ≥ 10.0.0&&< 10.2.1 | 10.2.1 |
| 📦npm | minimatch | ≥ 9.0.0&&< 9.0.6 | 9.0.6 |
| 📦npm | minimatch | ≥ 8.0.0&&< 8.0.5 | 8.0.5 |
| 📦npm | minimatch | ≥ 7.0.0&&< 7.4.7 | 7.4.7 |
| 📦npm | minimatch | ≥ 6.0.0&&< 6.2.1 | 6.2.1 |
| 📦npm | minimatch | ≥ 5.0.0&&< 5.1.7 | 5.1.7 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for minimatch. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update minimatch to 10.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-26996 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-26996 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-26996. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-26996 in your dependencies?
O3 detects CVE-2026-26996 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.