Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-64660: CWE-284: Improper Access Control in Microsoft Visual Studio Code

0
High
VulnerabilityCVE-2025-64660cvecve-2025-64660cwe-284
Published: Thu Nov 20 2025 (11/20/2025, 22:18:57 UTC)
Source: CVE Database V5
Vendor/Project: Microsoft
Product: Visual Studio Code

Description

Improper access control in GitHub Copilot and Visual Studio Code allows an authorized attacker to execute code over a network.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/27/2026, 06:54:25 UTC

Technical Analysis

CVE-2025-64660 is an improper access control vulnerability identified in Microsoft Visual Studio Code version 1.0.0, specifically affecting GitHub Copilot integration. The vulnerability stems from insufficient enforcement of access control policies, allowing an authorized attacker with limited privileges to execute arbitrary code remotely over a network. The CVSS 3.1 base score of 8.0 reflects the high impact on confidentiality, integrity, and availability, combined with low attack complexity and network attack vector. Exploitation requires some user interaction and privileges, but no known exploits have been reported in the wild as of the publication date. The vulnerability is categorized under CWE-284, which involves failures in access control mechanisms that can lead to unauthorized actions. This flaw could allow attackers to escalate privileges, execute malicious code, and potentially compromise entire development environments. Given Visual Studio Code's popularity as a cross-platform code editor used by millions of developers worldwide, the vulnerability presents a significant risk to software development pipelines and enterprise environments. The lack of available patches at the time of disclosure necessitates immediate mitigation efforts to reduce exposure.

Potential Impact

The impact of CVE-2025-64660 is substantial for organizations globally, particularly those relying on Visual Studio Code and GitHub Copilot for software development. Successful exploitation can lead to remote code execution, enabling attackers to gain unauthorized control over development machines and potentially pivot to other internal systems. This threatens the confidentiality of source code, intellectual property, and sensitive data, while also risking integrity through code tampering and availability through disruption of development workflows. Enterprises with continuous integration/continuous deployment (CI/CD) pipelines that incorporate Visual Studio Code are especially vulnerable to supply chain and insider threats. The vulnerability could facilitate advanced persistent threats (APTs) targeting software supply chains, increasing the risk of widespread malware distribution or data breaches. The absence of known exploits currently provides a window for proactive defense, but the high severity score underscores the urgency for mitigation.

Mitigation Recommendations

To mitigate CVE-2025-64660 effectively, organizations should implement the following specific measures: 1) Restrict network access to Visual Studio Code instances, especially those integrating GitHub Copilot, by using firewalls and network segmentation to limit exposure to trusted users and systems only. 2) Enforce the principle of least privilege by ensuring users operate with minimal necessary permissions, reducing the risk of privilege escalation. 3) Disable or limit GitHub Copilot features if not essential, as the vulnerability is linked to this integration. 4) Monitor logs and network traffic for unusual activities related to Visual Studio Code processes, including unexpected remote connections or code execution attempts. 5) Employ endpoint detection and response (EDR) solutions to detect anomalous behavior indicative of exploitation attempts. 6) Prepare for patch deployment by tracking vendor updates closely, and apply patches immediately once available. 7) Educate developers and IT staff about the vulnerability and safe usage practices to minimize user interaction risks. 8) Consider isolating development environments or using virtual machines/containers to contain potential compromises. These targeted actions go beyond generic advice and focus on reducing the attack surface and early detection.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
microsoft
Date Reserved
2025-11-06T23:40:37.275Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 691f98772b54a79d3490b34e

Added to database: 11/20/2025, 10:38:47 PM

Last enriched: 2/27/2026, 6:54:25 AM

Last updated: 3/26/2026, 7:56:41 AM

Views: 480

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses