Key points
- CVE-2026-81376 affects Visual Studio Code versions earlier than 1.136.2.
- Microsoft has released version 1.136.2, which fixes the security bypass.
- The flaw has a CVSS score of 9.6 and requires user interaction to exploit.
Visual Studio Code versions earlier than 1.136.2 contain a critical security flaw that allows attackers to bypass Workspace Trust protections. Microsoft has released version 1.136.2 to fix this issue. Users of older versions should update immediately to prevent potential remote code execution and data exposure.
In plain English
Workspace Trust is a safety feature designed to limit what Visual Studio Code can do when you open a project you have not reviewed. In Restricted Mode, the editor blocks features that could run code from that workspace. The flaw in older versions allows a specially prepared workspace to bypass these restrictions.
An attacker could use this bypass to connect to a service they control. If successful, the exploit could expose local data or run code with the permissions of the logged-in user. This is significant because developers often store credentials and access tokens on the same machine.
The background
Security researcher Sam Chen discovered the flaw and reported it to Microsoft. The company awarded him US$4,000 for the disclosure. The issue is tracked as CVE-2026-81376 and has a critical CVSS score of 9.6. Microsoft’s advisory describes it as an incomplete comparison with missing factors.
The National Vulnerability Database lists the flaw as a security feature bypass that can be triggered over a network. The CVSS vector indicates that user interaction is required, meaning the victim must take an action for the exploit to succeed. No malware campaign linked to this vulnerability has been identified.
What changes now
Microsoft has fixed the flaw in version 1.136.2. Users must update to this version or later to protect their systems. The full technical write-up from the researcher is not yet available, so exact exploit steps remain undisclosed. Teams should verify that all installations are updated to the patched version.
Who needs to act first
Teams usually prioritize systems that handle sensitive source code or cloud credentials. Check whether developers use older versions of the editor on workstations that access production environments. Roll out the update to exposed systems first, then test in a controlled group before a full deployment. Back up important project files before updating. Reduce exposure by restricting access to untrusted repositories until all systems are patched.
What to do and how to stay safe: Visual Studio Code
- Update Visual Studio Code to version 1.136.2 or later on all workstations.
- Verify that Workspace Trust is enabled in settings for all users.
- Monitor logs for unexpected network connections from the editor.
- Train staff to recognize suspicious workspace files or prompts.
Step-by-step guide: Out-of-Band Patches: Meaning, Risks, and Deployment Reality
General security guidance from the Patch Herald newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
Which versions of Visual Studio Code are affected?
Versions earlier than 1.136.2 are affected by CVE-2026-81376.
Is there a fix available?
Yes, Microsoft has released version 1.136.2, which fixes the flaw.
Does the exploit require user interaction?
Yes, the CVSS vector includes user interaction, meaning the victim must take an action.
