CVE-2026-58613

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-14. The CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Use after free in Windows Cloud Files Mini Filter Driver allows an authorized attacker to elevate privileges locally.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

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 (value × EchelonGraph’s weight)
Severity78% × 45%
The EG Score, 7.8 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.
EPSS PROB
0.4%
EPSS %ILE
29th
KEV
Not listed

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

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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

July 14, 2026

Last Modified

October 8, 2026

Advisory Details (1)

Auto-updated Jul 15, 2026
Patch available. Sources: microsoft.
MicrosoftMentions a patch (unverified)

Security Update Guide - Microsoft Security Response Center

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-58613

Vendor Advisories for CVE-2026-58613(2)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 53× 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 it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 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). Most recent first.

Showing the most recent 100 of 360 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 260 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  3. 2026-10-12 15:53 UTCEG score recompute
  4. 2026-10-11 19:36 UTCEG score recompute
  5. 2026-10-11 16:51 UTCEG score recompute
  6. 2026-10-11 14:14 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  10. 2026-10-08 19:15 UTCEG score recompute
  11. 2026-10-08 19:15 UTCVendor advisory
  12. 2026-10-08 19:15 UTCGHSA enrichmentGHSA-9f2j-4qc4-329w · GitHub severity HIGH · GitHub CVSS 7.8
  13. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  15. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  16. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  17. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  18. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  19. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  20. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  21. 2026-10-01 12:54 UTCEG score recompute
  22. 2026-10-01 12:54 UTCVendor advisory
  23. 2026-10-01 12:54 UTCGHSA enrichmentGHSA-9f2j-4qc4-329w · GitHub severity HIGH · GitHub CVSS 7.8
  24. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  25. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.4% · 29th percentile
Show 75 more
  1. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  2. 2026-09-28 08:58 UTCEG score recompute
  3. 2026-09-28 08:58 UTCVendor advisory
  4. 2026-09-28 08:58 UTCGHSA enrichmentGHSA-9f2j-4qc4-329w · GitHub severity HIGH · GitHub CVSS 7.8
  5. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  6. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  7. 2026-09-25 18:41 UTCEG score recompute
  8. 2026-09-25 18:41 UTCVendor advisory
  9. 2026-09-25 18:41 UTCGHSA enrichmentGHSA-9f2j-4qc4-329w · GitHub severity HIGH · GitHub CVSS 7.8
  10. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  11. 2026-09-24 09:03 UTCEG score recompute
  12. 2026-09-24 09:03 UTCVendor advisory
  13. 2026-09-24 09:03 UTCGHSA enrichmentGHSA-9f2j-4qc4-329w · GitHub severity HIGH · GitHub CVSS 7.8
  14. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  15. 2026-09-23 03:33 UTCEG score recompute
  16. 2026-09-23 03:33 UTCVendor advisory
  17. 2026-09-23 03:33 UTCGHSA enrichmentGHSA-9f2j-4qc4-329w · GitHub severity HIGH · GitHub CVSS 7.8
  18. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  19. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  20. 2026-09-18 10:48 UTCVendor advisory
  21. 2026-09-18 10:48 UTCGHSA enrichmentGHSA-9f2j-4qc4-329w · GitHub severity HIGH · GitHub CVSS 7.8
  22. 2026-09-17 22:54 UTCEG score recompute
  23. 2026-09-17 22:54 UTCVendor advisory
  24. 2026-09-17 22:53 UTCGHSA enrichmentGHSA-9f2j-4qc4-329w · GitHub severity HIGH · GitHub CVSS 7.8
  25. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  26. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  27. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  28. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  29. 2026-09-14 10:58 UTCVendor advisory
  30. 2026-09-14 10:58 UTCGHSA enrichmentGHSA-9f2j-4qc4-329w · GitHub severity HIGH · GitHub CVSS 7.8
  31. 2026-09-13 23:17 UTCEG score recompute
  32. 2026-09-13 23:17 UTCVendor advisory
  33. 2026-09-13 23:17 UTCGHSA enrichmentGHSA-9f2j-4qc4-329w · GitHub severity HIGH · GitHub CVSS 7.8
  34. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  35. 2026-09-13 07:41 UTCEG score recompute
  36. 2026-09-13 07:41 UTCVendor advisory
  37. 2026-09-13 07:41 UTCGHSA enrichmentGHSA-9f2j-4qc4-329w · GitHub severity HIGH · GitHub CVSS 7.8
  38. 2026-09-12 13:13 UTCVendor advisory
  39. 2026-09-12 13:13 UTCGHSA enrichmentGHSA-9f2j-4qc4-329w · GitHub severity HIGH · GitHub CVSS 7.8
  40. 2026-09-12 01:18 UTCEG score recompute
  41. 2026-09-12 01:18 UTCVendor advisory
  42. 2026-09-12 01:18 UTCGHSA enrichmentGHSA-9f2j-4qc4-329w · GitHub severity HIGH · GitHub CVSS 7.8
  43. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  44. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  45. 2026-09-09 21:07 UTCEG score recompute
  46. 2026-09-09 21:07 UTCVendor advisory
  47. 2026-09-09 21:07 UTCGHSA enrichmentGHSA-9f2j-4qc4-329w · GitHub severity HIGH · GitHub CVSS 7.8
  48. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  49. 2026-09-08 21:07 UTCGHSA enrichmentGHSA-9f2j-4qc4-329w · GitHub severity HIGH · GitHub CVSS 7.8
  50. 2026-09-08 17:21 UTCVendor advisory
  51. 2026-09-08 17:21 UTCGHSA enrichmentGHSA-9f2j-4qc4-329w · GitHub severity HIGH · GitHub CVSS 7.8
  52. 2026-09-08 01:14 UTCEG score recompute
  53. 2026-09-08 01:14 UTCVendor advisory
  54. 2026-09-08 01:14 UTCGHSA enrichmentGHSA-9f2j-4qc4-329w · GitHub severity HIGH · GitHub CVSS 7.8
  55. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  56. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  57. 2026-09-06 13:36 UTCVendor advisory
  58. 2026-09-06 13:35 UTCGHSA enrichmentGHSA-9f2j-4qc4-329w · GitHub severity HIGH · GitHub CVSS 7.8
  59. 2026-09-05 21:02 UTCEG score recompute
  60. 2026-09-05 21:02 UTCVendor advisory
  61. 2026-09-05 21:02 UTCGHSA enrichmentGHSA-9f2j-4qc4-329w · GitHub severity HIGH · GitHub CVSS 7.8
  62. 2026-09-04 22:40 UTCEG score recompute
  63. 2026-09-04 22:40 UTCVendor advisory
  64. 2026-09-04 22:40 UTCGHSA enrichmentGHSA-9f2j-4qc4-329w · GitHub severity HIGH · GitHub CVSS 7.8
  65. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  66. 2026-09-02 19:40 UTCEG score recompute
  67. 2026-09-02 19:40 UTCVendor advisory
  68. 2026-09-02 19:40 UTCGHSA enrichmentGHSA-9f2j-4qc4-329w · GitHub severity HIGH · GitHub CVSS 7.8
  69. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  70. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  71. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  72. 2026-08-31 15:41 UTCVendor advisory
  73. 2026-08-31 15:41 UTCGHSA enrichmentGHSA-9f2j-4qc4-329w · GitHub severity HIGH · GitHub CVSS 7.8
  74. 2026-08-31 04:44 UTCEG score recompute
  75. 2026-08-31 04:44 UTCVendor advisory

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-58613?
CVE-2026-58613 is a high-severity vulnerability; its CVE record was published on July 14, 2026. Use after free in Windows Cloud Files Mini Filter Driver allows an authorized attacker to elevate privileges locally.
When was CVE-2026-58613 made public?
CVE-2026-58613 was made public on July 14, 2026: that is the date its CVE record's CNA, Microsoft Corporation, gives for when the vulnerability was made public. The CVE record itself was published on July 14, 2026. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-58613 actively exploited?
CVE-2026-58613 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (29th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-58613?
CVE-2026-58613 has a CVSS base score of 7.8 (the CNA's own assessment, by microsoft; NVD's own analysis pending).
How do I remediate CVE-2026-58613?
A fix for CVE-2026-58613 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-58613 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-58613

Explore →

Is Your Infrastructure Affected by CVE-2026-58613?

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

Book a Demo →Browse All CVEs