CVE-2026-118764

MEDIUMPre-NVD 6.96.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (23rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — Patch released this week

Also known asEUVD-2026-113273 (ENISA EUVD) · GHSA-g3hv-75wg-m249 (GitHub Security Advisories)Source: ENISA EUVD

6.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

minimatch is a minimal matching utility for converting glob expressions into JavaScript RegExp objects. Starting in 7.0.0 and prior to 11.0.1, src/index.ts implements firstPhasePreProcess() so that, at optimizationLevel 2 or higher, it repeatedly expands attacker-controlled **/.. pattern segments inside a fixpoint loop, allowing generated globParts entries to be processed and expanded again. secondPhasePreProcess() then compares the expanded entries pairwise, so a short malicious glob can cause excessive CPU and memory consumption during pattern compilation. This issue is fixed in version 11.0.1.

CVSS
6.9
EG Score
6.9MEDIUMmedium confidence
EG Risk
46
EG Risk 46/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity69% × 45%
Impact severity (EG Severity): CVSS 6.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
23rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.9): severity, escalated by confirmed exploitation. This CVE's 6.9 is its impact severity (EG Severity), not escalated.

EG Severity
6.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 29, 2026

Last Modified

November 3, 2026

Advisory Details (2)

Auto-updated Oct 29, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

denial of service via globparts amplification · Advisory · isaacs/minimatch · GitHub

https://github.com/isaacs/minimatch/security/advisories/GHSA-g3hv-75wg-m249
GitHub commit

commit 77a0f5c4b80b (isaacs/minimatch)

Fix landed in isaacs/minimatch commit 77a0f5c4b80b — awaiting tagged release

https://github.com/isaacs/minimatch/commit/77a0f5c4b80bdc641c3c930a1d9edf5ad2db57f8

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatnodejs:24-9080020261105135730.rhel92026-11-09redhat
redhatnodejs24-main-24.22.2-0.2.hum12026-11-02redhat
redhatnodejs26-main-26.13.0-0.1.1.hum12026-11-02redhat
redhatnodejs22-main-22.23.4-2.3.2.3.1.hum12026-11-02redhat
npmminimatch @ 11.0.1 (fixes >= 7.0.0, < 11.0.1)—ghsa

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

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-minimatch5.1.1+~5.1.2-1 ... 9.0.7-2 (9 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-minimatch9.0.3-6, 9.0.7-1, 9.0.7-2
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-minimatch9.0.3-6, 9.0.7-1, 9.0.7-2
  • every version on: no fix on record
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
minimatch—
  • 7.0.0 up to 11.0.1: fixed in 11.0.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 29× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  2. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  3. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  4. 2026-11-11 06:55 UTCEchelonGraph re-scored
  5. 2026-11-11 06:55 UTCVendor advisory
  6. 2026-11-11 06:55 UTCGHSA enrichmentGHSA-g3hv-75wg-m249 · GitHub severity MODERATE
  7. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  8. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  9. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  10. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  11. 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  12. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  13. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  14. 2026-11-04 01:48 UTCVendor advisory
  15. 2026-11-04 01:48 UTCGHSA enrichmentGHSA-g3hv-75wg-m249 · GitHub severity MODERATE
  16. 2026-11-03 17:26 UTCEchelonGraph re-scored
  17. 2026-11-03 17:26 UTCVendor advisory
  18. 2026-11-03 17:26 UTCGHSA enrichmentGHSA-g3hv-75wg-m249 · GitHub severity MODERATE
  19. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  20. 2026-11-03 16:20 UTCEchelonGraph re-scored
  21. 2026-11-03 16:20 UTCVendor advisory
  22. 2026-11-03 16:20 UTCGHSA enrichmentGHSA-g3hv-75wg-m249 · GitHub severity MODERATE
  23. 2026-11-03 15:52 UTCEchelonGraph re-scored
  24. 2026-11-03 15:52 UTCVendor advisory
  25. 2026-11-03 15:52 UTCGHSA enrichmentGHSA-g3hv-75wg-m249 · GitHub severity MODERATE
Show 14 more
  1. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  2. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  3. 2026-11-01 07:59 UTCGHSA enrichmentGHSA-g3hv-75wg-m249 · GitHub severity MODERATE
  4. 2026-11-01 07:59 UTCEchelonGraph re-scored
  5. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  6. 2026-10-30 23:26 UTCEchelonGraph re-scored
  7. 2026-10-30 23:14 UTCEchelonGraph re-scored▼ 1.80
  8. 2026-10-30 23:13 UTCMITRE cvelistV5CVSS → 6.9 · CVSS v4 → 6.9 · severity → MEDIUM
  9. 2026-10-30 19:47 UTCEchelonGraph re-scored
  10. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  11. 2026-10-29 18:02 UTCENISA EUVD ID recordedEUVD-2026-113273 · Source: ENISA EUVD
  12. 2026-10-29 17:27 UTCEchelonGraph re-scored
  13. 2026-10-29 17:17 UTCEchelonGraph re-scoredFirst assessed: 8.7 HIGH
  14. 2026-10-29 17:16 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-118764?
CVE-2026-118764 is a medium-severity vulnerability; its CVE record was published on October 29, 2026. minimatch is a minimal matching utility for converting glob expressions into JavaScript RegExp objects. Starting in 7.0.0 and prior to 11.0.1, src/index.ts implements firstPhasePreProcess() so that, at optimizationLevel 2 or higher, it repeatedly expands attacker-controlled **/.. pattern segments…
When was the CVE record for CVE-2026-118764 published?
The CVE record for CVE-2026-118764 was published on October 29, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 3, 2026; the record at its source may have been updated since.
Is CVE-2026-118764 actively exploited?
CVE-2026-118764 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-118764?
CVE-2026-118764 has a CVSS base score of 6.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-118764?
A fix for CVE-2026-118764 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-118764 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-118764?

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