CVE-2026-50510

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
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 restriction of names for files and other resources in Github Copilot allows an unauthorized attacker to execute code locally.

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

Published

July 14, 2026

Last Modified

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

Vendor Advisories for CVE-2026-50510(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 19× in last 7d / 112× 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 305 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-50510?
CVE-2026-50510 is a high vulnerability published on July 14, 2026. Improper restriction of names for files and other resources in Github Copilot allows an unauthorized attacker to execute code locally.
When was CVE-2026-50510 disclosed?
CVE-2026-50510 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-50510 actively exploited?
CVE-2026-50510 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 70.3% of all scored CVEs.
What is the CVSS score of CVE-2026-50510?
CVE-2026-50510 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-50510?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50510, 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-50510

Explore →

Is Your Infrastructure Affected by CVE-2026-50510?

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

Start Free Scan →Browse All CVEs