Description
Not failing securely ('failing open') in Visual Studio Code allows an unauthorized attacker to bypass a security feature over a network.
Published: 2026-08-11
Score: 8.2 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Visual Studio Code does not enforce a required security check, causing a fail‑open behaviour that allows an attacker to bypass a security feature over a network. The flaw permits unauthorized access to protected functionality. This vulnerability is classified as CWE‑636, indicating that the problem arises from a failure to validate or sanitize input or safeguards, enabling a bypass of intended controls.

Affected Systems

Microsoft Visual Studio Code. Any installation that has not applied the patch announced by Microsoft is potentially vulnerable. No specific version range is provided, so all unpatched versions could be affected.

Risk and Exploitability

The CVSS score of 8.2 classifies this issue as high severity. The EPSS score is below 1%, suggesting that exploitation attempts are currently rare or unlikely. The vulnerability is not listed in the CISA KEV catalog. Based on the description, the likely attack vector is a remote network connection to the affected Visual Studio Code instance; an attacker would need to initiate or intercept a network session to exploit the fail‑open behaviour.

Generated by OpenCVE AI on August 12, 2026 at 20:20 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the latest Visual Studio Code update that includes the fix for CVE‑2026‑69306.
  • Restrict remote connections or disable the feature that triggers the vulnerable path until the update is installed.
  • Continuously monitor Microsoft’s security advisories for additional patches or work‑arounds related to this vulnerability.

Generated by OpenCVE AI on August 12, 2026 at 20:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 11 Aug 2026 20:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Tue, 11 Aug 2026 17:15:00 +0000

Type Values Removed Values Added
Description Not failing securely ('failing open') in Visual Studio Code allows an unauthorized attacker to bypass a security feature over a network.
Title Visual Studio Code Security Feature Bypass Vulnerability
First Time appeared Microsoft
Microsoft visual Studio Code
Weaknesses CWE-636
CPEs cpe:2.3:a:microsoft:visual_studio_code:*:*:*:*:*:*:*:*
Vendors & Products Microsoft
Microsoft visual Studio Code
References
Metrics cvssV3_1

{'score': 8.2, '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'}


Subscriptions

Microsoft Visual Studio Code
cve-icon MITRE

Status: PUBLISHED

Assigner: microsoft

Published:

Updated: 2026-08-31T20:05:59.803Z

Reserved: 2026-08-03T20:46:07.441Z

Link: CVE-2026-69306

cve-icon Vulnrichment

Updated: 2026-08-11T19:25:22.584Z

cve-icon NVD

Status : Analyzed

Published: 2026-08-11T17:19:07.000

Modified: 2026-08-28T20:19:38.273

Link: CVE-2026-69306

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-13T03:30:03Z

Weaknesses
  • CWE-636

    Not Failing Securely ('Failing Open')