CVE-2026-27904: Minimatch vulnerability (CVSS 7.5)

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.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityNone

IntegrityNone

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

Minimatch≥ 10.0.0 < 10.2.3 · ≥ 4.0.0 < 4.2.5 · ≥ 5.0.0 < 5.1.8 · ≥ 6.0.0 < 6.2.2

Remediation

Fixed in

Minimatch≥ 10.2.3

Patch & vendor advisories

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

References

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

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-27904 being actively exploited?

CVE-2026-27904 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.51%.

How severe is CVE-2026-27904?

CVE-2026-27904 has a CVSS 3.1 base score of 7.5, rated high. EPSS estimates a 0.51% probability of exploitation.

Which products are affected by CVE-2026-27904?

Affected products include Minimatch.

How do I fix CVE-2026-27904?

Upgrade affected software to a fixed version, for example Minimatch 10.2.3 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-27904 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo