CVE-2026-50353

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Use after free in Windows DirectX allows an authorized attacker to elevate privileges locally.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

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 (value × EchelonGraph’s weight)
Severity78% × 45%
The EG Score, 7.8 of 10.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
24th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 14, 2026

Last Modified

October 8, 2026

Advisory Details (1)

Auto-updated Jul 15, 2026
Patch available. Sources: microsoft.
MicrosoftMentions a patch (unverified)

Security Update Guide - Microsoft Security Response Center

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

Vendor Advisories for CVE-2026-50353(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 13× in last 7d / 49× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 347 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 247 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-50353?
CVE-2026-50353 is a high-severity vulnerability; its CVE record was published on July 14, 2026. Use after free in Windows DirectX allows an authorized attacker to elevate privileges locally.
When was CVE-2026-50353 made public?
CVE-2026-50353 was made public on July 14, 2026: that is the date its CVE record's CNA, Microsoft Corporation, gives for when the vulnerability was made public. The CVE record itself was published on July 14, 2026. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-50353 actively exploited?
CVE-2026-50353 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (24th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50353?
CVE-2026-50353 has a CVSS base score of 7.8 (the CNA's own assessment, by microsoft; NVD's own analysis pending).
How do I remediate CVE-2026-50353?
A fix for CVE-2026-50353 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-50353 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-50353?

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

Book a Demo →Browse All CVEs