Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

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

CVE-2026-27904GHSA-23c5-xmqv-rm74

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (minimatch 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.4), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm minimatch

    Affected
    >= 10.0.0, < 10.2.3>= 9.0.0, < 9.0.7>= 8.0.0, < 8.0.6>= 7.0.0, < 7.4.8>= 6.0.0, < 6.2.2>= 5.0.0, < 5.1.8>= 4.0.0, < 4.2.5< 3.1.4
    Fixed in
    7.4.8, 8.0.6, 4.2.5, 5.1.8, 10.2.3, 3.1.4, 6.2.2, 9.0.7

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
  • CVE-2026-27904: 0.53% estimated exploitation activity in the next 30 days; percentile 44.56 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary 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. --- Details The root cause is in AST.toRegExpSource() at src/ast.ts#L598. For the extglob type, the close token emitted is ) or )?, wrapping the recursive body in (?:...). When extglobs are nested, each level adds another quantifier around the previous group: This produces the following regexps: | Pattern | Generated regex | |----------------------|------------------------------------------| | (a\|b) | /^(?:a\|b)$/ | | ((a\|b)) | /^(?:(?:a\|b))$/ | | (((a\|b))) |…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-23c5-xmqv-rm74

  2. Revision 1 · created ·

    Published from osv record GHSA-23c5-xmqv-rm74

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-27904

Advisory: minimatch ReDoS: nested *() extglobs generate catastrophically backtracking regular expressions
IDs: CVE-2026-27904, GHSA-23c5-xmqv-rm74
Record: https://patchnext.com/advisories/cve-2026-27904 (revision 2, source checked 26 Oct 2026, 12:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: minimatch 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm minimatch: affected >= 10.0.0, < 10.2.3; >= 9.0.0, < 9.0.7; >= 8.0.0, < 8.0.6; >= 7.0.0, < 7.4.8; >= 6.0.0, < 6.2.2; >= 5.0.0, < 5.1.8; >= 4.0.0, < 4.2.5; < 3.1.4; fixed in 7.4.8, 8.0.6, 4.2.5, 5.1.8, 10.2.3, 3.1.4, 6.2.2, 9.0.7

## Suggested inspection (read-only)
- `npm ls minimatch --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on minimatch.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-23c5-xmqv-rm74 (OSV record GHSA-23c5-xmqv-rm74 lists affected ranges: npm minimatch >=10.0.0 =9.0.0 =8.0.0 =7.0.0 =6.0.0 =5.0.0 =4.0.0 =0 <3.1.4 (fixed))
- Verified: https://github.com/advisories/GHSA-23c5-xmqv-rm74 (GitHub-reviewed advisory GHSA-23c5-xmqv-rm74 lists affected ranges: npm minimatch >=10.0.0 =9.0.0 =8.0.0 =7.0.0 =6.0.0 =5.0.0 =4.0.0 =0 <3.1.4)

Commands are suggestions: review each one before running it.

Loading voting…