Microsoft Visual Studio Code up to 1.106.1 access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Microsoft Visual Studio Code up to 1.106.1. Affected by this issue is some unknown functionality. The manipulation leads to access control. This vulnerability is referenced as CVE-2025-64660. Remote exploitation of the attack is possible. No exploit is available. You should upgrade the affected component.
Details
A vulnerability was found in Microsoft Visual Studio Code up to 1.106.1. It has been rated as critical. This issue affects some unknown functionality. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Improper access control in GitHub Copilot and Visual Studio Code allows an authorized attacker to execute code over a network.
The advisory is shared at msrc.microsoft.com. The identification of this vulnerability is CVE-2025-64660 since 11/07/2025. The exploitation is known to be easy. The attack may be initiated remotely. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 11/27/2025). MITRE ATT&CK project uses the attack technique T1068 for this issue.
Upgrading to version 1.106.2 eliminates this vulnerability.
The vulnerability is also documented in the databases at EUVD (EUVD-2025-198368) and CERT Bund (WID-SEC-2025-2653). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Microsoft Visual Studio Code
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.microsoft.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.7VulDB Meta Temp Score: 6.6
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.0
CNA Vector (microsoft): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Access controlCWE: CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Visual Studio Code 1.106.2
Timeline
11/07/2025 CVE reserved11/21/2025 Advisory disclosed
11/21/2025 VulDB entry created
11/27/2025 VulDB entry last update
Sources
Vendor: microsoft.comAdvisory: msrc.microsoft.com
Status: Confirmed
CVE: CVE-2025-64660 (🔒)
GCVE (CVE): GCVE-0-2025-64660
GCVE (VulDB): GCVE-100-333125
EUVD: 🔒
CERT Bund: WID-SEC-2025-2653 - Microsoft Visual Studio Code: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen
Entry
Created: 11/21/2025 03:27Updated: 11/27/2025 10:22
Changes: 11/21/2025 03:27 (64), 11/21/2025 03:59 (1), 11/22/2025 13:06 (7), 11/27/2025 10:22 (6)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.