CVE-2026-27903

minimatch has a ReDoS: matchOne() combinatorial backtracking via multiple non-adjacent GLOBSTAR segments

HIGH
7.5
CVSS Score
Published: February 26, 2026 at 01:06 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
Severity
HIGH7.5
Exploit prediction
EPSS 0.6%
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.3, `matchOne()` performs unbounded recursive backtracking when a glob pattern contains multiple non-adjacent `**` (GLOBSTAR) segments and the input path does not match. The time complexity is O(C(n, k)) -- binomial -- where `n` is the number of path segments and `k` is the number of globstars. With k=11 and n=30, a call to the default `minimatch()` API stalls for roughly 5 seconds. With k=13, it exceeds 15 seconds. No memoization or call budget exists to bound this behavior. Any application where an attacker can influence the glob pattern passed to `minimatch()` is vulnerable. The realistic attack surface includes build tools and task runners that accept user-supplied glob arguments (ESLint, Webpack, Rollup config), multi-tenant systems where one tenant configures glob-based rules that run in a shared process, admin or developer interfaces that accept ignore-rule or filter configuration as globs, and CI/CD pipelines that evaluate user-submitted config files containing glob patterns. An attacker who can place a crafted pattern into any of these paths can stall the Node.js event loop for tens of seconds per invocation. The pattern is 56 bytes for a 5-second stall and does not require authentication in contexts where pattern input is part of the feature. 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.3 fix the issue.

Affected

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

v < 3.1.310.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
v < 10.2.3v < 3.1.3v < 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.3, 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:

References (1)

x_refsource_CONFIRMExploitVendor Advisory
Source: cverecord
https://github.com/isaacs/minimatch/security/advisories/GHSA-7r86-cg39-jmmj

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-407

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.

Free plan, no card