CVE-2026-69306 json
Visual Studio Code Security Feature Bypass Vulnerability
published 2026-08-11 2 mo ago modified 2026-10-30 9 d ago also EUVD-2026-56563
- cvss
- 8.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 45%
- public exploits
- 0
- none known
Summary
Not failing securely ('failing open') in Visual Studio Code allows an unauthorized attacker to bypass a security feature over a network.
Patch / fix
- Microsoft Visual Studio Code 1.132.1
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 mo ago
Exploit prediction
0.54% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N/E:U/RL:O/RC:C |
| CNA | 3.1 | 8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N |
Affected products
- Microsoft Visual Studio Code
Classification
- Weakness
-
- CWE-636 Not Failing Securely
References
-
msrc.microsoft.com
/update-guide/vulnerability/CVE-2026-69306
vendor-advisory, patch
Sources
- CVE List CVE-2026-69306
- NVD CVE-2026-69306
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.