CVE-2026-50519

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.9%, top 42% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

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

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

Initialization of a resource with an insecure default in GitHub Copilot and Visual Studio Code allows an unauthorized attacker to disclose information over a network.

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

Published

June 19, 2026

Last Modified

August 25, 2026

Advisory Details (1)

Auto-updated Jun 22, 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-50519

Vendor Advisories for CVE-2026-50519(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 34× in last 7d / 114× 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 216 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-50519?
CVE-2026-50519 is a high vulnerability published on June 19, 2026. Initialization of a resource with an insecure default in GitHub Copilot and Visual Studio Code allows an unauthorized attacker to disclose information over a network.
When was CVE-2026-50519 disclosed?
CVE-2026-50519 was first published in the National Vulnerability Database on June 19, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50519 actively exploited?
CVE-2026-50519 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 42.3% of all scored CVEs.
What is the CVSS score of CVE-2026-50519?
CVE-2026-50519 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-50519?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50519, 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-50519

Explore →

Is Your Infrastructure Affected by CVE-2026-50519?

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