CVE-2026-58527

HIGHNVD 7.07.8▲
EchelonGraph scoreHIGH 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 — 5 sources updated this week
7.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.0Exploit: NoneExposed: 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(high)
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
10.0%
KEV
Not listed

Published

July 14, 2026

Last Modified

July 24, 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 15× in last 7d / 32× 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-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:21 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-22 14:08 UTCEPSS rescore
  6. 2026-07-21 15:25 UTCEPSS rescore
  7. 2026-07-21 15:25 UTCEPSS rescore
  8. 2026-07-20 18:40 UTCNVD updateCVSS v3 → 7
  9. 2026-07-20 17:08 UTCEPSS rescore
  10. 2026-07-19 14:31 UTCEPSS rescore
  11. 2026-07-19 14:31 UTCEPSS rescore
  12. 2026-07-19 02:47 UTCEG score recompute
  13. 2026-07-19 02:47 UTCVendor advisory
  14. 2026-07-19 02:47 UTCGHSA enrichment
  15. 2026-07-19 02:29 UTCEPSS rescore
  16. 2026-07-18 10:04 UTCEPSS rescore
  17. 2026-07-17 05:02 UTCVendor advisory
  18. 2026-07-17 05:02 UTCGHSA enrichment
  19. 2026-07-16 17:11 UTCVendor advisory
  20. 2026-07-16 17:10 UTCGHSA enrichment
  21. 2026-07-16 17:03 UTCEPSS rescore
  22. 2026-07-16 05:18 UTCVendor advisory
  23. 2026-07-16 05:18 UTCGHSA enrichment
  24. 2026-07-15 17:26 UTCVendor advisory
  25. 2026-07-15 17:26 UTCGHSA enrichment
Show 7 more
  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 05:34 UTCVendor advisory
  4. 2026-07-15 05:34 UTCGHSA enrichment
  5. 2026-07-14 17:41 UTCEG score recompute
  6. 2026-07-14 17:41 UTCVendor advisory
  7. 2026-07-14 17:40 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

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 July 24, 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 10.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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.

Start Free Scan →Browse All CVEs