CVE-2026-50378

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 Key Guard 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-50378

Vendor Advisories for CVE-2026-50378(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 32× in last 7d / 173× 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 243 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-50378?
CVE-2026-50378 is a high vulnerability published on July 14, 2026. Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Key Guard allows an authorized attacker to elevate privileges locally.
When was CVE-2026-50378 disclosed?
CVE-2026-50378 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-50378 actively exploited?
CVE-2026-50378 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-50378?
CVE-2026-50378 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-50378?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50378, 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-50378

Explore →

Is Your Infrastructure Affected by CVE-2026-50378?

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