CVE-2026-50311

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

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: cna:microsoft, epss, ghsa
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.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Improper access control in Windows Server allows an authorized attacker to elevate privileges locally.

CVSS v3
7.8
EG Score
7.8(high)
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
16%
KEV
Not listed

Published

July 14, 2026

Last Modified

July 30, 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-50311

Vendor Advisories for CVE-2026-50311(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 42× in last 7d / 71× 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-31 10:07 UTCVendor advisory
  2. 2026-07-31 10:07 UTCGHSA enrichment
  3. 2026-07-30 20:56 UTCGHSA enrichment
  4. 2026-07-30 20:18 UTCGHSA enrichment
  5. 2026-07-30 18:23 UTCEG score recompute
  6. 2026-07-30 18:23 UTCVendor advisory
  7. 2026-07-30 18:22 UTCGHSA enrichment
  8. 2026-07-30 16:28 UTCEPSS rescore
  9. 2026-07-30 13:34 UTCEG score recompute
  10. 2026-07-30 13:34 UTCVendor advisory
  11. 2026-07-30 13:34 UTCGHSA enrichment
  12. 2026-07-30 01:30 UTCEPSS rescore
  13. 2026-07-30 00:21 UTCVendor advisory
  14. 2026-07-30 00:21 UTCGHSA enrichment
  15. 2026-07-29 11:11 UTCVendor advisory
  16. 2026-07-29 11:10 UTCGHSA enrichment
  17. 2026-07-28 21:59 UTCVendor advisory
  18. 2026-07-28 21:59 UTCGHSA enrichment
  19. 2026-07-28 16:10 UTCEG score recompute
  20. 2026-07-28 16:10 UTCVendor advisory
  21. 2026-07-28 16:09 UTCGHSA enrichment
  22. 2026-07-28 15:37 UTCEPSS rescore
  23. 2026-07-28 13:30 UTCVendor advisory
  24. 2026-07-28 13:30 UTCGHSA enrichment
  25. 2026-07-28 00:12 UTCVendor advisory
Show 46 more
  1. 2026-07-28 00:12 UTCGHSA enrichment
  2. 2026-07-27 22:36 UTCVendor advisory
  3. 2026-07-27 22:35 UTCGHSA enrichment
  4. 2026-07-27 16:33 UTCEG score recompute
  5. 2026-07-27 16:33 UTCVendor advisory
  6. 2026-07-27 16:33 UTCGHSA enrichment
  7. 2026-07-27 06:38 UTCVendor advisory
  8. 2026-07-27 06:38 UTCGHSA enrichment
  9. 2026-07-26 17:27 UTCEG score recompute
  10. 2026-07-26 17:27 UTCVendor advisory
  11. 2026-07-26 17:27 UTCGHSA enrichment
  12. 2026-07-26 14:54 UTCEPSS rescore
  13. 2026-07-26 04:59 UTCEG score recompute
  14. 2026-07-26 04:59 UTCVendor advisory
  15. 2026-07-26 04:58 UTCGHSA enrichment
  16. 2026-07-25 14:18 UTCEPSS rescore
  17. 2026-07-24 14:18 UTCEPSS rescore
  18. 2026-07-23 14:18 UTCEPSS rescore
  19. 2026-07-23 03:18 UTCEG score recompute
  20. 2026-07-22 14:08 UTCEPSS rescore
  21. 2026-07-21 15:25 UTCEPSS rescore
  22. 2026-07-20 17:08 UTCEPSS rescore
  23. 2026-07-19 14:31 UTCEPSS rescore
  24. 2026-07-19 14:31 UTCEPSS rescore
  25. 2026-07-19 03:27 UTCEG score recompute
  26. 2026-07-19 03:27 UTCVendor advisory
  27. 2026-07-19 03:27 UTCGHSA enrichment
  28. 2026-07-19 02:29 UTCEPSS rescore
  29. 2026-07-18 10:04 UTCEPSS rescore
  30. 2026-07-17 08:05 UTCEG score recompute
  31. 2026-07-17 08:05 UTCVendor advisory
  32. 2026-07-17 08:04 UTCGHSA enrichment
  33. 2026-07-16 21:53 UTCVendor advisory
  34. 2026-07-16 21:53 UTCGHSA enrichment
  35. 2026-07-16 17:03 UTCEPSS rescore
  36. 2026-07-16 08:43 UTCVendor advisory
  37. 2026-07-16 08:43 UTCGHSA enrichment
  38. 2026-07-15 19:32 UTCVendor advisory
  39. 2026-07-15 19:32 UTCGHSA enrichment
  40. 2026-07-15 16:57 UTCEPSS rescore
  41. 2026-07-15 16:57 UTCEPSS rescore
  42. 2026-07-15 06:21 UTCVendor advisory
  43. 2026-07-15 06:21 UTCGHSA enrichment
  44. 2026-07-14 17:11 UTCEG score recompute
  45. 2026-07-14 17:11 UTCVendor advisory
  46. 2026-07-14 17:10 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-50311?
CVE-2026-50311 is a high vulnerability published on July 14, 2026. Improper access control in Windows Server allows an authorized attacker to elevate privileges locally.
When was CVE-2026-50311 disclosed?
CVE-2026-50311 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50311 actively exploited?
CVE-2026-50311 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 84.5% of all scored CVEs.
What is the CVSS score of CVE-2026-50311?
CVE-2026-50311 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-50311?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50311, 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-50311

Explore →

Is Your Infrastructure Affected by CVE-2026-50311?

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

Start Free Scan →Browse All CVEs