CVE-2025-64660 Overview
CVE-2025-64660 is an improper access control vulnerability [CWE-284] affecting GitHub Copilot and Microsoft Visual Studio Code. An authorized attacker can exploit the flaw to execute code over a network against a vulnerable instance. Microsoft assigned this issue a high severity rating, reflecting the impact on confidentiality, integrity, and availability when exploitation succeeds.
The vulnerability requires the attacker to hold low privileges and convince a user to take an action, but it can be triggered remotely. Successful exploitation gives attackers code execution within the developer environment, which often holds source code, tokens, and cloud credentials.
Critical Impact
Authorized attackers can execute arbitrary code over the network through GitHub Copilot integration in Visual Studio Code, compromising developer workstations and connected source repositories.
Affected Products
- Microsoft Visual Studio Code
- GitHub Copilot extension for Visual Studio Code
- Developer environments integrating Copilot with Visual Studio Code workflows
Discovery Timeline
- 2025-11-20 - CVE-2025-64660 published to NVD
- 2025-11-26 - Last updated in NVD database
Technical Details for CVE-2025-64660
Vulnerability Analysis
The vulnerability stems from improper access control [CWE-284] within the integration between GitHub Copilot and Visual Studio Code. Access decisions enforced by the extension or its supporting services fail to adequately restrict who can trigger sensitive code execution paths. An authorized attacker with low-level privileges can bypass these controls to run code on the target system.
Exploitation requires user interaction, which typically takes the form of opening a crafted workspace, accepting a suggestion, or interacting with attacker-influenced content surfaced through Copilot. Once user interaction completes, the attacker gains code execution in the context of the Visual Studio Code process. This context frequently includes access to local source repositories, environment variables, SSH keys, and signed-in cloud sessions.
Root Cause
The root cause is missing or insufficient authorization enforcement on a code path reachable through the Copilot and Visual Studio Code integration. The control gap allows attacker-supplied input or actions to reach functionality that should be restricted to trusted callers, enabling code execution.
Attack Vector
The attack vector is network-based with low attack complexity. The adversary requires low-level privileges on a related service or account and must induce the target user to perform an action within Visual Studio Code. After interaction occurs, the flawed access control allows the attacker to execute code with the privileges of the Visual Studio Code process. Microsoft has not published a public proof of concept, and no exploitation in the wild has been confirmed.
The vulnerability is described in prose because no verified exploit code is currently published. Refer to the Microsoft CVE-2025-64660 Advisory for vendor technical details.
Detection Methods for CVE-2025-64660
Indicators of Compromise
- Unexpected child processes spawned by Code.exe or the Visual Studio Code helper processes, particularly shells, scripting interpreters, or curl/wget invocations.
- Outbound network connections from Visual Studio Code or Copilot extension processes to untrusted hosts shortly after a workspace was opened or a Copilot suggestion was accepted.
- Modification or creation of files in user profile directories, SSH key folders, or workspace .vscode configuration files by Visual Studio Code processes outside normal development activity.
Detection Strategies
- Build endpoint detection rules that flag process trees where Code.exe or the Copilot extension host launches command interpreters such as cmd.exe, powershell.exe, bash, or python.
- Correlate Copilot extension activity with file system writes to sensitive locations like ~/.ssh, ~/.aws, ~/.config, and credential stores.
- Inspect network telemetry for new domains contacted by developer endpoints immediately after Copilot interaction events.
Monitoring Recommendations
- Centralize Visual Studio Code and extension host logs into your SIEM and alert on unusual extension load events or auto-update activity for the Copilot extension.
- Monitor for installation of unsigned or sideloaded VSIX packages on developer workstations.
- Track Git operations and outbound pushes to repositories not previously seen for that developer to identify potential exfiltration.
How to Mitigate CVE-2025-64660
Immediate Actions Required
- Update Visual Studio Code and the GitHub Copilot extension to the latest versions referenced in the Microsoft advisory.
- Inventory all developer workstations running Visual Studio Code with Copilot enabled and prioritize patching for systems with access to production credentials or source repositories.
- Rotate developer-held secrets, including source control tokens and cloud access keys, if signs of exploitation are present.
Patch Information
Microsoft has published guidance for CVE-2025-64660 through the Microsoft CVE-2025-64660 Advisory. Apply the fixed versions of Visual Studio Code and the GitHub Copilot extension as listed in the advisory. Enterprises that manage Visual Studio Code through deployment tooling should push the update to all managed endpoints and verify the extension version after rollout.
Workarounds
- Disable or remove the GitHub Copilot extension on systems that cannot be patched immediately, especially those handling sensitive source code.
- Enforce a policy prohibiting the opening of untrusted workspaces and require Workspace Trust to remain enabled in Visual Studio Code settings.
- Restrict outbound network access from developer endpoints to known-good destinations until patching completes.
# Verify installed Visual Studio Code and Copilot extension versions
code --version
code --list-extensions --show-versions | grep -i copilot
# Update the Copilot extension from the command line
code --install-extension GitHub.copilot --force
code --install-extension GitHub.copilot-chat --force
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.


