CVE-2026-27903

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 59% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
50(Track)
EG Risk 50/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
43%
KEV
Not listed

Published

February 26, 2026

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Aug 4, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

ReDoS: matchOne() combinatorial backtracking via multiple non-adjacent GLOBSTAR segments · Advisory · isaacs/minimatch · GitHub

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

Vendor Advisories for CVE-2026-27903(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatodf4/rook-ceph-rhel9-operator:17829342842026-07-09redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
node-minimatch3.0.4+~3.0.3-1 ... 9.0.7-1 (17 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
node-minimatch5.1.1+~5.1.2-1 ... 9.0.7-2 (9 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-minimatch9.0.3-6, 9.0.7-1, 9.0.7-2
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-minimatch9.0.3-69.0.7-1
npm(1)
PackageVulnerable rangeFixed inDependents
minimatch3.1.3

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-17 19:30 UTCEPSS rescore
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-13 16:47 UTCEPSS rescore
  7. 2026-09-12 15:01 UTCEPSS rescore
  8. 2026-09-11 14:52 UTCEPSS rescore
  9. 2026-09-10 09:34 UTCEPSS rescore
  10. 2026-09-08 22:00 UTCEPSS rescore
  11. 2026-09-07 16:01 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-02 14:11 UTCEPSS rescore
  16. 2026-09-01 13:53 UTCEPSS rescore
  17. 2026-09-01 04:39 UTCEPSS rescore
  18. 2026-09-01 04:39 UTCEPSS rescore
  19. 2026-08-31 16:34 UTCOSV refresh
  20. 2026-08-30 19:17 UTCEPSS rescore
  21. 2026-08-30 01:22 UTCEPSS rescore
  22. 2026-08-28 21:41 UTCEPSS rescore
  23. 2026-08-27 14:25 UTCEPSS rescore
  24. 2026-08-26 14:46 UTCEPSS rescore
  25. 2026-08-25 13:48 UTCEPSS rescore
Show 50 more
  1. 2026-08-23 00:19 UTCEPSS rescore
  2. 2026-08-21 23:49 UTCEPSS rescore
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-18 13:48 UTCEPSS rescore
  6. 2026-08-17 13:47 UTCEPSS rescore
  7. 2026-08-16 14:56 UTCEPSS rescore
  8. 2026-08-16 02:14 UTCEPSS rescore
  9. 2026-08-15 01:30 UTCEPSS rescore
  10. 2026-08-14 21:10 UTCVendor advisory
  11. 2026-08-14 08:58 UTCEG score recompute
  12. 2026-08-14 08:58 UTCVendor advisory
  13. 2026-08-13 22:00 UTCEPSS rescore
  14. 2026-08-13 00:57 UTCEG score recompute
  15. 2026-08-13 00:57 UTCVendor advisory
  16. 2026-08-12 13:50 UTCEPSS rescore
  17. 2026-08-11 23:52 UTCEG score recompute
  18. 2026-08-11 23:52 UTCVendor advisory
  19. 2026-08-11 13:42 UTCEPSS rescore
  20. 2026-08-11 06:17 UTCEG score recompute
  21. 2026-08-11 06:17 UTCVendor advisory
  22. 2026-08-11 00:00 UTCEPSS rescore
  23. 2026-08-10 08:43 UTCVendor advisory
  24. 2026-08-09 19:43 UTCEG score recompute
  25. 2026-08-09 19:43 UTCVendor advisory
  26. 2026-08-09 13:46 UTCEPSS rescore
  27. 2026-08-09 08:35 UTCEG score recompute
  28. 2026-08-09 08:35 UTCVendor advisory
  29. 2026-08-08 16:37 UTCEPSS rescore
  30. 2026-08-08 07:46 UTCVendor advisory
  31. 2026-08-07 20:38 UTCEG score recompute
  32. 2026-08-07 20:38 UTCVendor advisory
  33. 2026-08-06 13:46 UTCEPSS rescore
  34. 2026-08-06 02:59 UTCEG score recompute
  35. 2026-08-06 02:59 UTCVendor advisory
  36. 2026-08-05 19:17 UTCEPSS rescore
  37. 2026-08-04 15:10 UTCEPSS rescore
  38. 2026-08-04 05:48 UTCEG score recompute
  39. 2026-08-04 05:48 UTCVendor advisory
  40. 2026-08-03 10:36 UTCEPSS rescore
  41. 2026-08-02 19:30 UTCEG score recompute
  42. 2026-08-02 19:30 UTCVendor advisory
  43. 2026-08-02 02:26 UTCEPSS rescore
  44. 2026-08-01 04:16 UTCEPSS rescore
  45. 2026-07-30 16:27 UTCEPSS rescore
  46. 2026-07-30 01:30 UTCEPSS rescore
  47. 2026-07-28 15:36 UTCEPSS rescore
  48. 2026-07-27 12:55 UTCEG score recompute
  49. 2026-07-27 12:55 UTCVendor advisory
  50. 2026-07-27 12:50 UTCOSV refresh

Frequently asked(5)

What is CVE-2026-27903?
CVE-2026-27903 is a high vulnerability published on February 26, 2026. 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)…
When was CVE-2026-27903 disclosed?
CVE-2026-27903 was first published in the National Vulnerability Database on February 26, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-27903 actively exploited?
CVE-2026-27903 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 57.0% of all scored CVEs.
What is the CVSS score of CVE-2026-27903?
CVE-2026-27903 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-27903?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-27903, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-27903

Explore →

Is Your Infrastructure Affected by CVE-2026-27903?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.