CVE-2026-69306

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

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

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

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

Not failing securely ('failing open') in Visual Studio Code allows an unauthorized attacker to bypass a security feature over a network.

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity82% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
35%
KEV
Not listed

Published

August 11, 2026

Last Modified

September 16, 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-69306

Vendor Advisories for CVE-2026-69306(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 37× in last 7d / 198× 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 318 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-69306?
CVE-2026-69306 is a high vulnerability published on August 11, 2026. Not failing securely ('failing open') in Visual Studio Code allows an unauthorized attacker to bypass a security feature over a network.
When was CVE-2026-69306 disclosed?
CVE-2026-69306 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-69306 actively exploited?
CVE-2026-69306 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 64.8% of all scored CVEs.
What is the CVSS score of CVE-2026-69306?
CVE-2026-69306 has a CVSS v4.0 base score of 8.2 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-69306?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-69306, 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-69306

Explore →

Is Your Infrastructure Affected by CVE-2026-69306?

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