CVE-2026-58650

HIGHNVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-11. 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.

Authorization bypass through user-controlled key in Visual Studio Code allows an unauthorized attacker to bypass a security feature 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
26%
KEV
Not listed

Published

August 11, 2026

Last Modified

August 19, 2026

Advisory Details (1)

Auto-updated Aug 11, 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-58650

Vendor Advisories for CVE-2026-58650(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 78× in last 7d / 110× 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 110 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-58650?
CVE-2026-58650 is a high vulnerability published on August 11, 2026. Authorization bypass through user-controlled key in Visual Studio Code allows an unauthorized attacker to bypass a security feature locally.
When was CVE-2026-58650 disclosed?
CVE-2026-58650 was first published in the National Vulnerability Database on August 11, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58650 actively exploited?
CVE-2026-58650 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 74.3% of all scored CVEs.
What is the CVSS score of CVE-2026-58650?
CVE-2026-58650 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-58650?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58650, 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-58650

Explore →

Is Your Infrastructure Affected by CVE-2026-58650?

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

Start Free Scan →Browse All CVEs