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-81357 Visual Studio Code Security Feature Bypass Vulnerability New On this page  CVE-2026-81357  Subscribe RSS PowerShell  API  CSAF Security Vulnerability Released: Sep 8, 2026 Assigning CNA Microsoft CVE.org link CVE-2026-81357  Impact Security Feature Bypass Max Severity Important Weakness CWE-918: Server-Side Request Forgery (SSRF) CVSS Source Microsoft Vector String 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 Metrics CVSS:3.1 8.2 / 7.1  Base score metrics: 8.2 / Temporal score metrics: 7.1  Expand all  Collapse all Metric Value   Base score metrics(8) Attack Vector Network Attack Complexity Low Privileges Required None User Interaction Required Scope Changed Confidentiality High Integrity Low Availability None   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 Server-side request forgery (ssrf) in Visual Studio Code allows an unauthorized attacker to bypass a security feature over a network. 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 Less Likely FAQ What security feature could be bypassed by successfully exploiting this vulnerability? An attacker who successfully exploited this vulnerability could bypass the network access restrictions enforced for the Visual Studio Code agent, allowing outbound connections to resources that the configured policy is intended to block. How could an attacker exploit this vulnerability? An attacker could influence content processed by the Visual Studio Code agent so that it requests a specially crafted URL. Successful exploitation could bypass configured network restrictions and allow access to resources that the policy is intended to block. User interaction is required to run the agent against attacker-controlled content. Acknowledgements Dimitris Chatzis 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: Sep 8, 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.136.2 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 Sep 8, 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