Summary
Impact: Security Feature Bypass. Microsoft rating: Important. Not known to be exploited — Exploitation Less Likely. Customer action: Required.
Details
How could an attacker exploit this vulnerability?
An attacker could convince a user to open a specially crafted Visual Studio Code workspace. The workspace could cause Visual Studio Code to connect to an attacker-controlled service and bypass Workspace Trust restrictions. Successful exploitation could allow the attacker to access local data or execute code in the context of the user. User interaction is required, but the user does not need to trust the workspace.
What security feature could be bypassed by successfully exploiting this vulnerability?
An attacker who successfully exploited this vulnerability could bypass the Visual Studio Code Workspace Trust feature, allowing content from an untrusted workspace to run commands or code without the user first granting trust. See Workspace Trust for more information.
According to the CVSS metric, a successful exploitation could lead to a scope change (S:C). What does this mean for this vulnerability?
In this case, a successful attack can break out of the Visual Studio Code Workspace Trust feature. See Workspace Trust for more information.
Security updates
1.136.2 — https://code.visualstudio.com/updates/v1_136
Vulnerabilities 1
-
Critical 9.6
Visual Studio Code Security Feature Bypass Vulnerability
Incomplete comparison with missing factors in Visual Studio Code allows an unauthorized attacker to bypass a security feature over a network.
Revision history
-
#1
Information published.
References
-
CVE-2026-81376 Visual Studio Code Security Feature Bypass Vulnerability - HTML
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-81376
-
Microsoft Exploitability Index
https://www.microsoft.com/en-us/msrc/exploitability-index?rtc=1
-
Microsoft Support Lifecycle
https://support.microsoft.com/lifecycle
-
Common Vulnerability Scoring System
https://www.first.org/cvss