Security News

Cybersecurity news aggregator

🔓
HIGH Vulnerabilities Microsoft Security Response Center

CVE-2026-58650 Visual Studio Code Security Feature Bypass Vulnerability

CVE-2026-58650 is an Important-severity authorization bypass (CWE-639) in Visual Studio Code with a CVSS 3.1 score of 7.8. The vulnerability allows a local attacker to bypass the Workspace Trust security feature, enabling code execution from an untrusted workspace without user consent.
Read Full Article →

We use optional cookies to improve your experience on our websites, such as through social media connections, and to display personalized advertising based on your online activity. If you reject optional cookies, only cookies necessary to provide you the services will be used. You may change your selection by clicking “Manage Cookies” at the bottom of the page. Privacy Statement Third-Party Cookies AcceptRejectManage cookies MSRC  Customer Guidance  Security Update Guide  Vulnerabilities  CVE-2026-58650 Visual Studio Code Security Feature Bypass Vulnerability New On this page  CVE-2026-58650  Subscribe RSS PowerShell  API  CSAF Security Vulnerability Released: Aug 11, 2026 Assigning CNA Microsoft CVE.org link CVE-2026-58650  Impact Security Feature Bypass Max Severity Important Weakness CWE-639: Authorization Bypass Through User-Controlled Key CVSS Source Microsoft Vector String CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C Metrics CVSS:3.1 7.8 / 6.8  Base score metrics: 7.8 / Temporal score metrics: 6.8  Expand all  Collapse all Metric Value   Base score metrics(8) Attack Vector Local Attack Complexity Low Privileges Required None User Interaction Required Scope Unchanged Confidentiality High Integrity High Availability High   Temporal score metrics(3) Exploit Code Maturity Unproven Remediation Level Official Fix Report Confidence Confirmed Please see Common Vulnerability Scoring System for more information on the definition of these metrics. Executive Summary Authorization bypass through user-controlled key in Visual Studio Code allows an unauthorized attacker to bypass a security feature locally. Exploitability The following table provides an exploitability assessment for this vulnerability at the time of original publication. Publicly disclosed No Exploited No Exploitability assessment Exploitation More Likely FAQ 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. Acknowledgements 陳宥升 (CheN..) https://github.com/samer666569 Microsoft recognizes the efforts of those in the security community who help us protect customers through coordinated vulnerability disclosure. See Acknowledgements for more information. Security Updates To determine the support lifecycle for your software, see the Microsoft Support Lifecycle. Release date Descending  Edit columns  Download  Filters  Product Family  Max Severity  Impact  Platform   Clear Release date  Product Platform Impact Max Severity Article Download Build Number Assigning CNA Title: Release date, Content: Aug 11, 2026 Visual Studio Code - Security Feature Bypass Important Title: Knowledge Base Articles for Visual Studio Code, Content:, 1 link Release Notes  Title: Download Security Update for Visual Studio Code, Content:, 1 link Security Update  Title: Build numbers, Content: 1.132.1 Title: Assigning CNA, Content: Microsoft All results loaded Loaded all 1 rows Disclaimer The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply. Revisions version revisionDate description 1.0 Aug 11, 2026 Information published.  How satisfied are you with the MSRC Security Update Guide? Rating  Broken  Bad  Below average  Average  Great!  Your Privacy Choices Consumer Health Privacy Privacy & Cookies

Share this article