CVE-2026-27904

minimatch ReDoS: nested *() extglobs generate catastrophically backtracking regular expressions

HIGH

7.5

CVSS Score

Published: February 26, 2026 at 01:07 AM UTC

Updated: June 17, 2026 at 10:27 AM UTC

2 products affected across 2 vendorsMinimatchMinimatch

Using minimatch by isaacs?

Get instant alerts when new vulnerabilities affect minimatch - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH7.5

Exploit prediction

EPSS 0.5%

SSVC

PoC

Description

minimatch is a minimal matching utility for converting glob expressions into JavaScript RegExp objects. Prior to version 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, and 3.1.4, nested `*()` extglobs produce regexps with nested unbounded quantifiers (e.g. `(?:(?:a|b)*)*`), which exhibit catastrophic backtracking in V8. With a 12-byte pattern `*(*(*(a|b)))` and an 18-byte non-matching input, `minimatch()` stalls for over 7 seconds. Adding a single nesting level or a few input characters pushes this to minutes. This is the most severe finding: it is triggered by the default `minimatch()` API with no special options, and the minimum viable pattern is only 12 bytes. The same issue affects `+()` extglobs equally. Versions 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, and 3.1.4 fix the issue.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Minimatch · Minimatch Projectnpm

95%

v < 3.1.410.0.0 ≤ v < 10.2.34.0.0 ≤ v < 4.2.55.0.0 ≤ v < 5.1.86.0.0 ≤ v < 6.2.27.0.0 ≤ v < 7.4.88.0.0 ≤ v < 8.0.69.0.0 ≤ v < 9.0.7

Minimatch · Isaacs

60%

v < 10.2.3v < 3.1.4v < 4.2.5v < 5.1.8v < 6.2.2v < 7.4.8v < 8.0.6v < 9.0.7

Affected range stops below 10.2.3, so it looks safe — our inference, not a vendor statement

Affected range stops below 3.1.4, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.2.5, so it looks safe — our inference, not a vendor statement

Affected range stops below 5.1.8, so it looks safe — our inference, not a vendor statement

Affected range stops below 6.2.2, so it looks safe — our inference, not a vendor statement

Affected range stops below 7.4.8, so it looks safe — our inference, not a vendor statement

Affected range stops below 8.0.6, so it looks safe — our inference, not a vendor statement

Affected range stops below 9.0.7, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

https://github.com/isaacs/minimatch/security/advisories/GHSA-23c5-xmqv-rm74

References (1)

x_refsource_CONFIRMExploitVendor Advisory

Source: cverecord

https://github.com/isaacs/minimatch/security/advisories/GHSA-23c5-xmqv-rm74

SSVC — Action Prioritization

SSVCPoCNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHGitHub_M

Attack Vector: NETWORK
Complexity: LOW
Privileges: NONE
User Interaction: NONE
Scope: UNCHANGED
Confidentiality: NONE
Integrity: NONE
Availability: HIGH

Vector?

Quick Info

StatusANALYZED

CWE

CWE-1333

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card