CVE-2026-70335

Think of Visual Studio Code as a command “switchboard” that helps run actions on your computer. This flaw can be tricked so that, when a user interacts with a malicious Copilot/CODE workflow, it runs attacker-chosen commands—like replacing the switchboard instructions with a malicious one. That can allow an attacker to take over what the app is allowed to do on that machine.

This matters if your business uses Visual Studio Code, especially with GitHub Copilot, on machines where an attacker could get local access (for example, through a shared device, compromised workstation, or malicious content that influences user interaction). The risk is mainly for scenarios where a local attacker can induce user interaction with a malicious payload inside Copilot or Visual Studio Code. If the attacker can’t reach your machine locally or can’t cause the user interaction, the exposure is much lower.

This is RED because the flaw is about executing arbitrary operating system commands and is triggered by user interaction, and the fix is already available. Even though no clear, dated incidents are reported publicly for this CVE, the involvement of a well-known target (Visual Studio Code) and recent actor attention means you should treat it as active patch-priority work.

1. Confirm exposure (your side)

   • On each affected machine, open Visual Studio Code and check the installed version (Help → About).
   • If the version is older than 1.132.1, you are potentially exposed.

2. Apply the fix

   • Upgrade Visual Studio Code to 1.132.1 (or later).
   • Microsoft’s update guidance is here: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-70335

3. Temporary containment if you cannot patch immediately

   • Restrict who can use those developer machines and avoid shared/untrusted devices.
   • Reduce the chance of malicious user interaction by not opening untrusted repositories/projects or files that you don’t trust.
   • Be cautious with Copilot-driven actions/suggestions that originate from unknown content; if something looks suspicious, don’t follow it.

4. After patching

   • Look for any recent signs of unusual command execution tied to editor workflows (for example, unexpected processes spawned soon after using Copilot or handling a project).
   • Ensure endpoint protections are enabled (so that if anything attempted to run, it would be blocked and logged).

5. What to monitor

   • Logs/alerts from your endpoint security about newly executed commands/processes originating from or triggered by Visual Studio Code.
   • Any repeated attempts that look like command execution tied to specific projects or work sessions.

6. KEV and exploitation status note

   • This CVE is not listed in CISA KEV, and there are no clearly dated press incidents reported in the provided findings. Still, because the traffic-light verdict is RED and a patch exists, patching is the primary action.

Severity is high (CVSS 7.8) and the weakness is CWE-78 (improper neutralization of special elements used in an OS command), which is consistent with operating-system command injection behavior. The attack vector is local and requires no authentication, but it does require user interaction to get a malicious payload executed within GitHub Copilot or Visual Studio Code. There is no public exploit code listed in the provided findings, and CISA KEV does not include this CVE, so exploitation status is not confirmed via those channels. The patch is available in Visual Studio Code 1.132.1. EPSS is reported as a low predicted likelihood with a flat trend, but since the system verdict is RED and actor attention (PULSE) is noted, prioritize the upgrade regardless. “KEV” here means inclusion in CISA’s Known Exploited Vulnerabilities catalog, which would indicate confirmed real-world exploitation; it is not listed for this CVE in the provided findings.