CVE-2026-50414

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 54% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
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: 1%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 Media allows an authorized attacker to elevate privileges over a network.

CVSS v3
8.8
EG Score
8.8(medium)
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%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
46%
KEV
Not listed

Published

July 14, 2026

Last Modified

September 17, 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-50414

Vendor Advisories for CVE-2026-50414(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 7× in last 7d / 94× 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 290 total refreshes for this CVE.

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

Frequently asked(5)

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

Explore →

Is Your Infrastructure Affected by CVE-2026-50414?

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