CVE-2026-69306

HIGHPre-NVD 8.28.2—
EchelonGraph scoreHIGH 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(high)
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
34%
KEV
Not listed

Published

August 11, 2026

Last Modified

August 20, 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 86× in last 7d / 131× 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 131 total refreshes for this CVE.

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

Start Free Scan →Browse All CVEs