Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-69306: CWE-636: Not Failing Securely ('Failing Open') in Microsoft Visual Studio Code

0
High
VulnerabilityCVE-2026-69306cvecve-2026-69306cwe-636
Published: 08/11/2026 (08/11/2026, 17:05:18 UTC)
Source: CVE Database V5
Vendor/Project: Microsoft
Product: Visual Studio Code

Description

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

CVSS v3.1

Score 8.2high

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None
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

Affected software

GitHub Actionsmore threats →ai
microsoft/vscode
pkg:github/microsoft/vscode
Affected versions
=1.0.0

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 08/11/2026, 17:42:25 UTC

Technical Analysis

This vulnerability in Visual Studio Code (CVE-2026-69306) involves a failure to fail securely ('failing open'), which permits an unauthorized attacker to bypass a security feature remotely. The flaw is identified as CWE-636. The CVSS v3.1 base score is 8.2, reflecting high severity with network attack vector, low attack complexity, no privileges required, and user interaction required. The impact includes high confidentiality loss and low integrity loss without availability impact. Microsoft has published an official fix for this issue.

Potential Impact

An attacker can bypass a security feature in Visual Studio Code remotely, potentially leading to unauthorized access to confidential information and partial integrity compromise. There is no impact on availability. The vulnerability requires user interaction but no privileges or complex attack conditions.

Mitigation Recommendations

An official fix is available from Microsoft. Users and administrators should apply the vendor-provided patch as detailed in the Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-69306 to remediate this vulnerability.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
microsoft
Date Reserved
2026-08-03T20:46:07.441Z
Cvss Version
3.1
State
PUBLISHED
Remediation Level
official-fix
Vendor Advisory Urls
[{"url":"https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-69306","vendor":"Microsoft"}]

Threat ID: 6a7b583cbf8831d539156719

Added to database: 08/11/2026, 17:13:32 UTC

Last enriched: 08/11/2026, 17:42:25 UTC

Last updated: 08/12/2026, 00:12:10 UTC

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses