CVE-2026-50385

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 4 sources updated this week
8.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: 8.8Exploit: 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
8.8
EG Score
8.8(high)
EG Risk
40(Track)
EG Risk 40/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
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

July 14, 2026

Last Modified

July 28, 2026

Advisory Details (1)

Auto-updated Jul 14, 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-50385

Vendor Advisories for CVE-2026-50385(2)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 30× in last 7d / 54× 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-29 10:57 UTCVendor advisory
  2. 2026-07-29 10:57 UTCGHSA enrichment
  3. 2026-07-28 21:48 UTCVendor advisory
  4. 2026-07-28 21:48 UTCGHSA enrichment
  5. 2026-07-28 16:02 UTCEG score recompute
  6. 2026-07-28 16:02 UTCVendor advisory
  7. 2026-07-28 16:02 UTCGHSA enrichment
  8. 2026-07-28 15:37 UTCEPSS rescore
  9. 2026-07-28 13:20 UTCVendor advisory
  10. 2026-07-28 13:20 UTCGHSA enrichment
  11. 2026-07-28 00:09 UTCVendor advisory
  12. 2026-07-28 00:09 UTCGHSA enrichment
  13. 2026-07-27 22:30 UTCVendor advisory
  14. 2026-07-27 22:30 UTCGHSA enrichment
  15. 2026-07-27 16:30 UTCEG score recompute
  16. 2026-07-27 16:30 UTCVendor advisory
  17. 2026-07-27 16:30 UTCGHSA enrichment
  18. 2026-07-27 07:17 UTCVendor advisory
  19. 2026-07-27 07:17 UTCGHSA enrichment
  20. 2026-07-26 18:07 UTCEG score recompute
  21. 2026-07-26 18:07 UTCVendor advisory
  22. 2026-07-26 18:07 UTCGHSA enrichment
  23. 2026-07-26 14:54 UTCEPSS rescore
  24. 2026-07-26 04:53 UTCEG score recompute
  25. 2026-07-26 04:53 UTCVendor advisory
Show 29 more
  1. 2026-07-26 04:52 UTCGHSA enrichment
  2. 2026-07-25 14:18 UTCEPSS rescore
  3. 2026-07-24 14:18 UTCEPSS rescore
  4. 2026-07-23 14:18 UTCEPSS rescore
  5. 2026-07-23 03:18 UTCEG score recompute
  6. 2026-07-22 14:08 UTCEPSS rescore
  7. 2026-07-21 15:25 UTCEPSS rescore
  8. 2026-07-20 17:08 UTCEPSS rescore
  9. 2026-07-19 14:31 UTCEPSS rescore
  10. 2026-07-19 14:31 UTCEPSS rescore
  11. 2026-07-19 03:09 UTCEG score recompute
  12. 2026-07-19 03:09 UTCVendor advisory
  13. 2026-07-19 03:09 UTCGHSA enrichment
  14. 2026-07-19 02:29 UTCEPSS rescore
  15. 2026-07-18 10:04 UTCEPSS rescore
  16. 2026-07-16 22:25 UTCVendor advisory
  17. 2026-07-16 22:25 UTCGHSA enrichment
  18. 2026-07-16 17:03 UTCEPSS rescore
  19. 2026-07-16 09:16 UTCVendor advisory
  20. 2026-07-16 09:16 UTCGHSA enrichment
  21. 2026-07-15 20:07 UTCVendor advisory
  22. 2026-07-15 20:07 UTCGHSA enrichment
  23. 2026-07-15 16:57 UTCEPSS rescore
  24. 2026-07-15 16:57 UTCEPSS rescore
  25. 2026-07-15 06:57 UTCVendor advisory
  26. 2026-07-15 06:57 UTCGHSA enrichment
  27. 2026-07-14 17:48 UTCEG score recompute
  28. 2026-07-14 17:48 UTCVendor advisory
  29. 2026-07-14 17:40 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-50385?
CVE-2026-50385 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-50385 disclosed?
CVE-2026-50385 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on July 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-50385 actively exploited?
CVE-2026-50385 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 91.7% of all scored CVEs.
What is the CVSS score of CVE-2026-50385?
CVE-2026-50385 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-50385?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50385, 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-50385

Explore →

Is Your Infrastructure Affected by CVE-2026-50385?

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