For software engineers, system administrators, and DevSecOps teams managing developer workstations, this advisory carries a clear mandate: Customer action required: Yes. Because the flaw enables a bypass of Workspace Trust protections simply by opening a malicious workspace—even when the user never clicks "trust"—updating Visual Studio Code to fixed build 1.141.1 or later is essential.
Vulnerability Overview and Official MSRC Telemetry
According to the Microsoft Security Response Center (MSRC) advisory, the core description of CVE-2026-70098 is straightforward: "Missing authorization in Visual Studio Code allows an unauthorized attacker to execute code over a network."
Below is the complete breakdown of the official telemetry and status indicators provided by Microsoft for this vulnerability:
- CVE ID: CVE-2026-70098
- Title: Visual Studio Code Remote Code Execution Vulnerability
- Severity: Important
- CVSS Base Score: 8.8
- CVSS Temporal Score: 7.7
- CVSS Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C - Weakness Classification: CWE-862 (Missing Authorization)
- Exploitation Assessment: Exploitation Less Likely
- Publicly disclosed: No
- Exploited: No
- Customer action required: Yes
Affected Products and Remediation Matrix
| Affected Product | Fixed Build | Official Remediation |
|---|---|---|
| Visual Studio Code | 1.141.1 | For Visual Studio Code, update to fixed build 1.141.1 or later. |
Section Summary: CVE-2026-70098 is an Important-severity remote code execution flaw (CVSS 8.8 base, 7.7 temporal) in Visual Studio Code caused by CWE-862. It is neither publicly disclosed nor actively exploited, and Microsoft assesses exploitation as less likely, but customer action is required to update to fixed build 1.141.1.
How the Attack Works: Bypassing Workspace Trust Without Consent
Why does a bug that requires user interaction still command an 8.8 base score? The answer lies in how modern developers work and how this specific flaw subverts a primary defensive boundary.
In its official advisory FAQ, Microsoft explains the exact mechanics of the threat:
Let us unpack what that means in a real-world engineering workflow. In general industry practice, developers routinely clone external repositories, review pull requests from outside contributors, download reproduction cases attached to bug reports, or inspect archived projects during security audits. Workspace Trust was engineered specifically for this scenario: when you open an unfamiliar folder or workspace in Restricted Mode, Visual Studio Code is supposed to block automatic task execution, disable potentially dangerous workspace settings, and restrict extensions from running untrusted code until you explicitly grant trust.
Because CVE-2026-70098 involves missing authorization (CWE-862), a specially crafted workspace can slip past those Restricted Mode guardrails. The required user interaction (UI:R in the CVSS vector) is minimal—merely opening the workspace in Visual Studio Code. The developer does not need to click through a security prompt or approve trust for the workspace. Once opened, the attacker-controlled content can execute arbitrary code in the context of the current user.
Decoding the CVSS Vector
Looking closely at the CVSS v3.1 vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C) highlights why security teams should treat this seriously despite the "Exploitation Less Likely" assessment:
- Attack Vector: Network (
AV:N) & Attack Complexity: Low (AC:L): The malicious workspace can be delivered over the network (such as via a remote repository or file share) and does not require complex race conditions or specialized environment preparation to trigger. - Privileges Required: None (
PR:N) & User Interaction: Required (UI:R): The attacker needs no prior access to the victim's system; they only need to persuade a user to open the crafted workspace. - High Impact Across the Board (
C:H/I:H/A:H): Because the code runs in the context of the logged-in user, a compromise on a developer machine is rarely low-impact. Synthesizing from general cybersecurity knowledge, a developer's user context typically holds SSH keys, cloud provider CLI tokens, source code credentials, and local administrative or container privileges. Compromising that user session gives an attacker complete confidentiality, integrity, and availability control over everything that user account can touch. - Temporal Modifiers (
E:U/RL:O/RC:C): The temporal score drops to 7.7 because exploit maturity is unproven (E:U), an official fix is available (RL:O), and report confidence is confirmed (RC:C).
Section Summary: While an attacker must convince a developer to open a crafted workspace, CVE-2026-70098 neutralizes Workspace Trust protections so that code executes automatically in the user's context without the user ever granting trust.
Remediation and Practical Guidance for IT and Developers
Microsoft's remediation requirement is explicit: For Visual Studio Code, update to fixed build 1.141.1 or later.
Because developer tools are frequently installed in user space rather than system-wide directories, enterprise patch management teams often have blind spots when tracking Visual Studio Code versions across their fleet. Here is how individual users and IT administrators should respond:
- Verify Your Installed Build: Open Visual Studio Code, navigate to the Help menu, and select About (or check via your endpoint management inventory) to verify that the version is 1.141.1 or later.
- Apply the Update Immediately: If your installation is below build 1.141.1, trigger the built-in update mechanism (
Help > Check for Updates) and restart the editor to complete the installation, or deploy the updated package via your organization's software management pipeline. - Exercise Caution with Untrusted Repositories Until Patched: Until you have confirmed that build 1.141.1 or later is running, do not rely on Workspace Trust (Restricted Mode) to protect your workstation when opening unfamiliar workspaces or third-party repositories.
Section Summary: Every Visual Studio Code installation should be updated to fixed build 1.141.1 or later immediately, as Restricted Mode cannot be relied upon to block malicious workspaces on unpatched versions.