CVE-2026-50650

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.8 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.5% (38th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from the CNA's CVSS
Sources: the CNA's CVSS, EPSS
Trending — 3 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.5%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Improper control of generation of code ('code injection') in .NET Framework allows an unauthorized 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.5% × 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.5%
EPSS %ILE
38th
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 14, 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-50650

Vendor Advisories for CVE-2026-50650(18)

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

Patch Availability(16)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatdotnet8.0-0:8.0.130-1.el9_62026-08-24redhat
redhatdotnet9.0-0:9.0.120-1.el10_02026-08-24redhat
redhatdotnet8.0-0:8.0.130-1.el9_42026-08-24redhat
redhatdotnet9.0-0:9.0.120-1.el9_62026-08-24redhat
redhatdotnet8.0-0:8.0.130-1.el10_02026-08-24redhat
redhatdotnet8-0-main-8.0.129-2.1.hum12026-07-20redhat
redhatdotnet8.0-0:8.0.129-1.el10_22026-07-20redhat
redhatdotnet9.0-0:9.0.119-1.el8_102026-07-20redhat
redhatdotnet10.0-0:10.0.110-1.el8_102026-07-20redhat
redhatdotnet8.0-0:8.0.129-1.el8_102026-07-20redhat
redhatdotnet9.0-0:9.0.119-1.el9_82026-07-20redhat
redhatdotnet9.0-0:9.0.119-1.el10_22026-07-20redhat
redhatdotnet10.0-0:10.0.110-1.el10_22026-07-20redhat
redhatdotnet8.0-0:8.0.129-1.el9_82026-07-20redhat
redhatdotnet10.0-0:10.0.110-1.el9_82026-07-20redhat
redhatdotnet9-0-main-9.0.118-1.hum12026-06-19redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 1 ecosystem)
NuGet(3)
PackageVulnerable rangeFix by version rangeDependents
Microsoft.WindowsDesktop.App.Runtime.win-arm648.0.0 ... 8.0.8 (28 versions)
  • 10.0.0 up to 10.0.10: fixed in 10.0.10
  • 9.0.0 up to 9.0.18: fixed in 9.0.18
  • 8.0.0 up to 8.0.29: fixed in 8.0.29
—
Microsoft.WindowsDesktop.App.Runtime.win-x648.0.0 ... 8.0.8 (28 versions)
  • 10.0.0 up to 10.0.10: fixed in 10.0.10
  • 9.0.0 up to 9.0.18: fixed in 9.0.18
  • 8.0.0 up to 8.0.29: fixed in 8.0.29
—
Microsoft.WindowsDesktop.App.Runtime.win-x868.0.0 ... 8.0.8 (28 versions)
  • 10.0.0 up to 10.0.10: fixed in 10.0.10
  • 9.0.0 up to 9.0.18: fixed in 9.0.18
  • 8.0.0 up to 8.0.29: fixed in 8.0.29
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 42× 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 249 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 149 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.5% · 38th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 38th 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:20 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  10. 2026-10-08 19:15 UTCEG score recompute
  11. 2026-10-08 19:15 UTCVendor advisory
  12. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  15. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  16. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  17. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  18. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  19. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  20. 2026-10-01 12:53 UTCEG score recompute
  21. 2026-10-01 12:53 UTCVendor advisory
  22. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  23. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  24. 2026-09-28 08:54 UTCEG score recompute
  25. 2026-09-28 08:54 UTCVendor advisory
Show 75 more
  1. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  2. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  3. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  4. 2026-09-25 18:40 UTCEG score recompute
  5. 2026-09-25 18:40 UTCVendor advisory
  6. 2026-09-24 09:01 UTCEG score recompute
  7. 2026-09-24 09:01 UTCVendor advisory
  8. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  9. 2026-09-23 03:29 UTCEG score recompute
  10. 2026-09-23 03:29 UTCVendor advisory
  11. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  12. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  13. 2026-09-18 10:09 UTCVendor advisory
  14. 2026-09-17 22:45 UTCEG score recompute
  15. 2026-09-17 22:45 UTCVendor advisory
  16. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  17. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  18. 2026-09-14 10:57 UTCVendor advisory
  19. 2026-09-13 23:16 UTCEG score recompute
  20. 2026-09-13 23:16 UTCVendor advisory
  21. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  22. 2026-09-13 07:39 UTCEG score recompute
  23. 2026-09-13 07:39 UTCVendor advisory
  24. 2026-09-12 13:12 UTCVendor advisory
  25. 2026-09-11 21:55 UTCEG score recompute
  26. 2026-09-11 21:55 UTCVendor advisory
  27. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  28. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  29. 2026-09-09 21:07 UTCVendor advisory
  30. 2026-09-08 22:41 UTCEG score recompute
  31. 2026-09-08 22:41 UTCVendor advisory
  32. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  33. 2026-09-08 21:06 UTCVendor advisory
  34. 2026-09-08 17:16 UTCVendor advisory
  35. 2026-09-08 01:11 UTCEG score recompute
  36. 2026-09-08 01:11 UTCVendor advisory
  37. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  38. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  39. 2026-09-06 13:32 UTCVendor advisory
  40. 2026-09-05 21:00 UTCEG score recompute
  41. 2026-09-05 21:00 UTCVendor advisory
  42. 2026-09-04 22:38 UTCEG score recompute
  43. 2026-09-04 22:38 UTCVendor advisory
  44. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  45. 2026-09-02 18:42 UTCEG score recompute
  46. 2026-09-02 18:42 UTCVendor advisory
  47. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  48. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  49. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  50. 2026-08-31 15:39 UTCVendor advisory
  51. 2026-08-31 04:40 UTCEG score recompute
  52. 2026-08-31 04:40 UTCVendor advisory
  53. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  54. 2026-08-30 16:10 UTCVendor advisory
  55. 2026-08-30 04:13 UTCEG score recompute
  56. 2026-08-30 04:13 UTCVendor advisory
  57. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  58. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  59. 2026-08-28 21:10 UTCVendor advisory
  60. 2026-08-28 01:53 UTCEG score recompute
  61. 2026-08-28 01:53 UTCVendor advisory
  62. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  63. 2026-08-27 12:55 UTCVendor advisory
  64. 2026-08-26 23:36 UTCEG score recompute
  65. 2026-08-26 23:36 UTCVendor advisory
  66. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  67. 2026-08-26 12:12 UTCVendor advisory
  68. 2026-08-25 21:10 UTCEG score recompute
  69. 2026-08-25 21:10 UTCVendor advisory
  70. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  71. 2026-08-25 08:52 UTCVendor advisory
  72. 2026-08-24 21:08 UTCEG score recompute
  73. 2026-08-24 21:08 UTCVendor advisory
  74. 2026-08-24 12:37 UTCEG score recompute
  75. 2026-08-24 12:37 UTCVendor advisory

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-50650?
CVE-2026-50650 is a high-severity vulnerability; its CVE record was published on July 14, 2026. Improper control of generation of code ('code injection') in .NET Framework allows an unauthorized attacker to elevate privileges locally.
When was CVE-2026-50650 made public?
CVE-2026-50650 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-50650 actively exploited?
CVE-2026-50650 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50650?
CVE-2026-50650 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-50650?
A fix for CVE-2026-50650 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-50650 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-50650

Explore →

Is Your Infrastructure Affected by CVE-2026-50650?

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

Book a Demo →Browse All CVEs