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

Exp

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.

Published: 2026-02-26 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-27903 is rated Exploit Available (59/100): CVSS High severity, with low exploitation likelihood (EPSS 0.50%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2026-27903

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2026-27903

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.02% 0.50% +0.48%
2 2026-03-21 0.05% 0.02% -0.03%
3 2026-03-04 — 0.05% —

Full EPSS history (4 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-27903

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2026-27903

GitHub Security Advisory for CVE-2026-27903

GHSA-7r86-cg39-jmmj · Severity: high · Ecosystem: npm — minimatch has ReDoS: matchOne() combinatorial backtracking via multiple non-adjacent GLOBSTAR segments

OS Trackers for CVE-2026-27903

vendor priority summary link
debian not yet assigned CVE-2026-27903 not yet assigned priority: Debian including 1 source packages (node-minimatch), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 3, resolved 2. https://security-tracker.debian.org/tracker/CVE-2026-27903
redhat medium — https://access.redhat.com/security/cve/CVE-2026-27903
ubuntu medium CVE-2026-27903 medium priority: Ubuntu including 1 source packages (node-minimatch), 8 status rows across 8 suites (bionic, focal, jammy, noble, questing, trusty, upstream, xenial): needs-triage 8. https://ubuntu.com/security/CVE-2026-27903

Affected software / configurations for CVE-2026-27903

Vendor Product Version Raw CPE
minimatch_project minimatch < 3.1.3 cpe:2.3:a:minimatch_project:minimatch:*:*:*:*:*:node.js:*:*
minimatch_project minimatch >= 4.0.0, < 4.2.5 cpe:2.3:a:minimatch_project:minimatch:*:*:*:*:*:node.js:*:*
minimatch_project minimatch >= 5.0.0, < 5.1.8 cpe:2.3:a:minimatch_project:minimatch:*:*:*:*:*:node.js:*:*
minimatch_project minimatch >= 6.0.0, < 6.2.2 cpe:2.3:a:minimatch_project:minimatch:*:*:*:*:*:node.js:*:*
minimatch_project minimatch >= 7.0.0, < 7.4.8 cpe:2.3:a:minimatch_project:minimatch:*:*:*:*:*:node.js:*:*
minimatch_project minimatch >= 8.0.0, < 8.0.6 cpe:2.3:a:minimatch_project:minimatch:*:*:*:*:*:node.js:*:*
minimatch_project minimatch >= 9.0.0, < 9.0.7 cpe:2.3:a:minimatch_project:minimatch:*:*:*:*:*:node.js:*:*
minimatch_project minimatch >= 10.0.0, < 10.2.3 cpe:2.3:a:minimatch_project:minimatch:*:*:*:*:*:node.js:*:*

References for CVE-2026-27903

cvelogic Threat Intelligence