CVE-2026-58527

HIGHNVD 7.07.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-14. NVD baseline CVSS 7.0; sources differ by 0.8.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.0Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Runtime allows an authorized attacker to elevate privileges locally.

CVSS v3
7.0
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/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
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

July 14, 2026

Last Modified

August 28, 2026

Advisory Details (1)

Auto-updated Jul 15, 2026
Patch available. Sources: microsoft.
microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

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

Vendor Advisories for CVE-2026-58527(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 35× in last 7d / 175× 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.

Showing the most recent 100 of 252 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-58527?
CVE-2026-58527 is a high vulnerability published on July 14, 2026. Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Runtime allows an authorized attacker to elevate privileges locally.
When was CVE-2026-58527 disclosed?
CVE-2026-58527 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58527 actively exploited?
CVE-2026-58527 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 88.4% of all scored CVEs.
What is the CVSS score of CVE-2026-58527?
CVE-2026-58527 has a CVSS v3 base score of 7.0 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.8.
How do I remediate CVE-2026-58527?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58527, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-58527?

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