CVE-2026-69306
Not failing securely ('failing open') in Visual Studio Code allows an unauthorized attacker to bypass a security feature over a network.
Scoring
- Severity
- HIGH
- CVSS base score
- 8.2
- CVSS vector
- 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
- EPSS probability
- 0.41%
- CWE
- CWE-636
- Published
- 2026-08-11
- Last modified
- 2026-09-16
Affected products
- Microsoft Visual Studio Code
Weakness type
Related vulnerabilities
- CVE-2026-22034 — Snuffleupagus vulnerable to RCE on instances with upload validation enabled but without the VLD package
- CVE-2021-1578 — Cisco Application Policy Infrastructure Controller Privilege Escalation Vulnerability
- CVE-2025-54870 — VTun-ng's failure to initialize encryption modules may cause reversion to plaintext
- CVE-2023-4030 — A vulnerability was reported in BIOS for ThinkPad P14s Gen 2, P15s Gen 2, T14 Gen 2, and T15 Gen 2 that could cause the
- CVE-2026-53913 — Apache Camel Keycloak: KeycloakSecurityPolicy verifies the bearer access token only inside its role and permission checks, so in the default configuration the token is never verified and any non-null bearer value is accepted
- CVE-2026-53459 — Bambuddy's authentication fails open on database errors, allowing unauthenticated access to all endpoints
- CVE-2026-73421 — NextAuth.js: Configuration errors can cause existence-based auth checks to fail open (auth object populated with an error)
- CVE-2026-40525 — OpenViking < 0.3.9 Authentication Bypass via VikingBot OpenAPI