CVE-2026-50516

CRITICALPre-NVD 9.49.4
EchelonGraph scoreMEDIUM confidence

Score 9.4 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-11. the CNA's CVSS baseline 9.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 4 sources updated this week
9.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.4Exploit: None knownExposed: 0

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

Missing authentication for critical function in Microsoft Azure Kubernetes Service allows an unauthorized attacker to elevate privileges over a network.

CVSS v3
9.4
EG Score
9.4(medium)
EG Risk
58(Track)
EG Risk 58/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
Severity94% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
56%
KEV
Not listed

Published

August 11, 2026

Last Modified

September 16, 2026

Advisory Details (1)

Auto-updated Sep 17, 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-50516

Vendor Advisories for CVE-2026-50516(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 80× in last 7d / 366× 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 567 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-50516?
CVE-2026-50516 is a critical vulnerability published on August 11, 2026. Missing authentication for critical function in Microsoft Azure Kubernetes Service allows an unauthorized attacker to elevate privileges over a network.
When was CVE-2026-50516 disclosed?
CVE-2026-50516 was first published in the National Vulnerability Database on August 11, 2026, with the most recent update on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50516 actively exploited?
CVE-2026-50516 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 43.8% of all scored CVEs.
What is the CVSS score of CVE-2026-50516?
CVE-2026-50516 has a CVSS v4.0 base score of 9.4 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-50516?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50516, 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-50516

Explore →

Is Your Infrastructure Affected by CVE-2026-50516?

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