Security Update for Microsoft Visual Studio Code (April 2025)

The version of Microsoft Visual Studio Code installed on the remote host is prior to 1.100.1. It is, therefore, affected by a vulnerability where files or directories accessible to external parties in Visual Studio Code allows an unauthorized attacker to bypass a security feature locally. Note th...

CVE-2025-21264

Files or directories accessible to external parties in Visual Studio Code allows an unauthorized attacker to bypass a security feature locally...

CVE-2025-21264

Files or directories accessible to external parties in Visual Studio Code allows an unauthorized attacker to bypass a security feature locally...

CVE-2025-21264 Visual Studio Code Security Feature Bypass Vulnerability

...

CVE-2025-21264 Visual Studio Code Security Feature Bypass Vulnerability

...

CVE-2025-21264

Visual Studio Code (VS Code) is affected by CVE-2025-21264, a local vulnerability described as a security feature bypass. The issue permits an unauthorized, local attacker to bypass a security feature due to how VS Code handles files/directories accessible to external parties and trusted domains....

CVE-2025-21264

creationtimestamp| type| source ---|---|--- 2025-05-13 16:27:02+00:00| seen| https://www.thezdi.com/blog/2025/5/13/the-may-2025-security-update-review 2025-05-13 18:30:45+00:00| seen| https://t.me/DarkWebInformerCVEAlerts/16179 2025-06-17 18:48:36+00:00| seen|...

KLA90915 SB vulnerability in Microsoft Visual Studio Code

A security feature bypass vulnerability was found in Microsoft Visual Studio Code. Malicious users can exploit this vulnerability to bypass security restrictions. Original advisories CVE-2025-21264 Exploitation Related products Microsoft-Visual-Studio Visual-Studio-Code Microsoft-Visual-Studio-Co...

Security Update for Microsoft Visual Studio Code (May 2025)

The version of Microsoft Visual Studio Code installed on the remote Windows host is prior to 1.100.1. It is, therefore, affected by an unspecified security feature bypass vulnerability. Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported...