Visual Studio Code
Monthly
Remote code execution in Markdown Preview Enhanced (a Visual Studio Code Markdown preview extension) before 0.8.29 lets a malicious repository run operating-system commands as the victim's account the moment the victim opens a Markdown file from that repository. The extension automatically evaluates repository-controlled .crossnote/config.js and .crossnote/parser.js files through vm.runInNewContext, and prototype-chain traversal escapes the Node.js host realm to reach the Function constructor and the process object - no further interaction and no module-scoped require are needed, and both the configuration-evaluation and parser-hook paths are affected. The vector requires local placement of the repository plus user interaction (opening the file), so it is not mass-exploitable over the network against a default install; there is no CISA KEV listing and no public exploit identified at time of analysis. The issue is fixed in Markdown Preview Enhanced 0.8.29, which bundles crossnote 0.9.30.
Remote code execution in Visual Studio Code (versions 1.0.0 up to but not including 1.141.1) is achievable through a path traversal flaw when a victim opens a crafted workspace, folder, or repository containing malicious pathnames that escape the intended restricted directory. The attack is unauthenticated (PR:N) but requires user interaction (UI:R), and the scope change (S:C) alongside high confidentiality, integrity, and availability impacts yields a CVSS score of 9.6. Microsoft has released a vendor patch (1.141.1); no public exploit code has been identified at time of analysis, though the severity warrants prompt patching.
Remote code execution in Visual Studio Code versions 1.0.0 through 1.141.1 allows an unauthenticated, network-positioned attacker to execute arbitrary code when a victim opens attacker-controlled content (e.g., a crafted workspace, folder, or repository), due to improper output encoding/escaping (CWE-116). Exploitation requires user interaction, and no public exploit code has been identified at time of analysis. The vendor has released a patch in version 1.141.1.
An unauthenticated, network-positioned attacker can bypass a security feature in Visual Studio Code versions 1.0.0 up to but not including 1.141.1 by getting a victim to open or interact with attacker-controlled content, resulting in high confidentiality impact (CVSS 7.4, S:C/C:H/I:N/A:N). The user-interaction requirement (UI:R) is the primary limiting factor - the flaw cannot be triggered fully passively and no privileges or local access are needed once the victim interacts. Neither KEV confirmation nor public exploit code has been identified at time of analysis, so this is a moderate-priority patching item rather than an emergency, though the scope-changed, high-confidentiality rating keeps it above routine maintenance.
Command injection in Visual Studio Code 1.0.0 through 1.141.0 allows an unauthenticated remote attacker to execute arbitrary code in the context of the editor when a developer opens attacker-controlled content such as a malicious workspace, folder, repository, or project configuration file. Exploitation depends on user interaction (a victim must open the crafted project), but is otherwise low-complexity with high confidentiality, integrity, and availability impact; no public exploit code has been identified at the time of analysis. Microsoft has released a vendor fix in Visual Studio Code 1.141.1.
Missing authorization in Visual Studio Code lets a local attacker bypass a security feature once the victim opens attacker-controlled content, such as a crafted workspace, folder, or file, producing high confidentiality, integrity, and availability impact (CVSS 3.1 base 7.8, AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). No pre-existing privileges or authentication are required, but exploitation demands local delivery of the malicious content plus mandatory user interaction, which rules out remote, unattended, or automated mass exploitation. No public exploit code has been identified at time of analysis, and the specific security feature being bypassed is not detailed in the available data and should be confirmed against the Microsoft MSRC advisory.
Improper resolution of path equivalence (CWE-41) in Visual Studio Code allows an unauthenticated local attacker to bypass a security feature, likely Workspace Trust or restricted mode, by convincing a victim to open and interact with a crafted workspace or folder. The vulnerability requires user interaction and high attack complexity, and while it has a CVSS score of 7.7 (High), it is a moderate-priority developer-workstation issue rather than an internet-facing emergency. No public exploit code has been identified at time of analysis, and the exact affected versions should be confirmed via the linked Microsoft advisory.
Information disclosure in Visual Studio Code allows an unauthenticated remote attacker to exfiltrate sensitive data via a crafted file or workspace that triggers incorrect name or reference resolution (CWE-706). Affected versions span 1.0.0 through all releases before 1.136.2. The scope change (S:C) in the CVSS vector indicates the confidentiality impact reaches beyond the VS Code process itself - potentially exposing system files, environment variables, or workspace secrets to a remote origin. No public exploit code or KEV listing is identified at time of analysis, but the broad affected version range and VS Code's developer-centric user base make this a meaningful supply-chain adjacent risk.
Insufficient protection of stored or transmitted credentials in GitHub Copilot and Visual Studio Code before 1.136.2 allows a network-positioned attacker to disclose sensitive information, including authentication tokens, with a CVSS base score of 7.5 (AV:N/AC:L/PR:N/UI:N/C:H/I:N/A:N). Microsoft (secure@microsoft.com) is the assigning CNA and a vendored patch is available, but CISA SSVC rates exploitation as 'none' and automatable as 'no', and EPSS is only 0.62% (47th percentile), indicating elevated theoretical severity without observed attacker activity. No public exploit code has been identified at time of analysis.
Security feature bypass in Visual Studio Code before 1.136.2 allows a remote, unauthenticated attacker to circumvent a protection mechanism via a failing-open (CWE-636) code path, resulting in high confidentiality impact and limited integrity impact across a changed scope. The vulnerability is reachable over the network with low complexity but requires user interaction, suggesting an attacker must induce the victim to open a crafted workspace, file, or URI. No public exploit code and no CISA KEV listing have been identified at time of analysis, though Microsoft has released a patch.
Security feature bypass in Visual Studio Code (versions 1.0.0 through below 1.136.2) allows a remote unauthenticated attacker to circumvent a protective security control via an interpretation conflict in the editor's processing pipeline. The vulnerability requires user interaction (UI:R) - a victim must open or interact with attacker-influenced content - after which the scope change (S:C) and high confidentiality impact suggest sensitive host data or credentials may be exfiltrated beyond the process boundary. No public exploit or CISA KEV listing has been identified at time of analysis.
Security-feature bypass in Microsoft Visual Studio Code before 1.136.2 lets a remote, unauthenticated attacker defeat a protection mechanism when a user is lured into interacting with malicious content (UI:R). Rooted in an incomplete comparison that omits required factors (CWE-693), the flaw carries a scope-changed CVSS 9.6 with full confidentiality, integrity, and availability impact, consistent with a trust/security-control bypass that can extend beyond the editor's initial boundary. A vendor patch exists; no public exploit is identified at time of analysis.
Server-side request forgery in Visual Studio Code prior to 1.136.2 allows a remote unauthenticated attacker to bypass security features and force VS Code to issue HTTP requests to internal or otherwise restricted network resources on the victim's behalf. Exploitation requires user interaction - a developer must open or trigger attacker-controlled content within VS Code - after which the editor acts as a request proxy, crossing trust boundaries (S:C) to reach endpoints inaccessible from the attacker's network position. No public exploit code or active CISA KEV listing has been identified at time of analysis; however, developers are high-value targets due to their typical privileged network access to internal infrastructure.
HTTP request smuggling in Visual Studio Code (versions 1.0.0 through 1.136.2) enables unauthenticated network attackers to bypass security controls through inconsistent interpretation of HTTP request boundaries. The CVSS scope change (S:C) signals that impact extends beyond the editor itself - smuggled requests can affect back-end services or proxies that VS Code communicates with, resulting in high confidentiality exposure. No public exploit code or CISA KEV listing has been identified at time of analysis, but the network-accessible, unauthenticated nature of the attack surface warrants prompt patching.
Authorization bypass in Visual Studio Code versions 1.0.0 through 1.136.1 allows an unauthenticated network attacker to circumvent a security feature via a user-controlled key (CWE-639), with user interaction required to trigger exploitation. The CVSS 8.8 score reflects full impact across confidentiality, integrity, and availability (C:H/I:H/A:H), indicating potential complete compromise of the affected VS Code instance. A vendor-released patch is available in version 1.136.2 per the Microsoft Security Response Center; no public exploit code or CISA KEV listing has been identified at time of analysis.
Path traversal in Visual Studio Code versions prior to 1.136.2 enables a remote unauthenticated attacker - contingent on user interaction - to escape the editor's restricted directory boundary and read sensitive files from the host system, effectively bypassing a security feature such as workspace trust or sandbox isolation. The vulnerability carries a CVSS 7.4 with Scope:Changed and C:H, reflecting that the impact crosses from VS Code's own context into broader host file system access. No public exploit code or CISA KEV listing has been identified at time of analysis.
Security feature bypass in Visual Studio Code before 1.136.2 allows a local attacker to circumvent an input-validation blocklist (CWE-184), resulting in high confidentiality, integrity, and availability impact. The vulnerability requires user interaction - most plausibly opening a crafted workspace or file - but no elevated privileges. Microsoft shipped a vendor patch capping affected versions below 1.136.2; no public exploit or CISA KEV listing has been identified at time of analysis.
Remote code execution in Microsoft Visual Studio Code allows a network-based attacker to inject and execute arbitrary code on a victim's machine with no prior authentication, provided the victim performs a user interaction - such as opening a malicious workspace, file, or URI. Classified under CWE-94 (Code Injection), the vulnerability carries a CVSS base score of 8.8, reflecting high impact across confidentiality, integrity, and availability. No public exploit code or CISA KEV listing was identified at the time of analysis, but the attack complexity is rated Low, making reliable exploitation straightforward once a victim is lured.
OS command injection in GitHub Copilot and Visual Studio Code enables a local unauthorized attacker to escalate privileges on the affected developer workstation, achieving full High impact across confidentiality, integrity, and availability. The CWE-78 root cause indicates that attacker-influenced input containing shell metacharacters is improperly incorporated into OS-level command execution within one or both products, triggering upon a user action such as opening a malicious file or repository. No public exploit code has been identified and this vulnerability has not been confirmed actively exploited by CISA KEV at time of analysis; however, the local privilege escalation path on widely deployed developer tooling represents a meaningful risk in supply chain and social engineering scenarios.
OS command injection in Visual Studio Code exposes victims to remote code execution when they interact with attacker-controlled content, such as a malicious workspace, repository, or file. The vulnerability (CWE-78) stems from improper neutralization of shell metacharacters in input passed to OS-level command execution routines, giving an unauthenticated network attacker the ability to run arbitrary commands with the privileges of the VS Code process. No active exploitation has been confirmed by CISA KEV, and no public proof-of-concept is referenced at time of analysis.
Fail-open security logic in Visual Studio Code permits network-based security feature bypass by an unauthenticated attacker who can induce user interaction. The root cause is CWE-636: when the application encounters an error or edge condition in a security enforcement path, it defaults to granting rather than denying access, neutralizing the intended control. With a CVSS score of 8.2 and a scope-changed vector (S:C) paired with high confidentiality impact, successful exploitation could expose data or capabilities beyond the direct VS Code process boundary. No public exploit code or CISA KEV listing has been identified at time of analysis.
Local security feature bypass in Visual Studio Code allows an attacker with local access to circumvent an authorization control, achieving high-impact compromise of confidentiality, integrity, and availability on the affected system. The vulnerability (CWE-693, Protection Mechanism Failure) is exploitable locally without elevated privileges but requires user interaction, making social engineering or physical access the likely delivery path. No public exploit code or active exploitation has been identified at time of analysis.
Remote code execution in Visual Studio Code (versions 1.0.0 through 1.132.0) is enabled by a missing authorization check (CWE-862) on a network-accessible code path, allowing an unauthenticated network attacker to execute arbitrary code on a victim's machine with high impact across confidentiality, integrity, and availability. Exploitation requires user interaction (CVSS UI:R), meaning the victim must engage with attacker-controlled content. A vendor-released patch is available in version 1.132.1; no public exploit code or CISA KEV listing is confirmed at time of analysis.
Security feature bypass in Visual Studio Code (versions 1.0.0 through 1.132.1) exploits CWE-639, where authorization decisions rely on attacker-controllable keys, allowing a local attacker to circumvent an intended access control with high impact across confidentiality, integrity, and availability. The attack requires no elevated attacker privileges but does require a legitimate VS Code user to interact with the manipulated environment, pointing to shared-workstation or social-engineering delivery paths. No public exploit code has been identified and this CVE is absent from the CISA KEV catalog at time of analysis; a vendor-released patch is available at version 1.132.1.
Security feature bypass in the Python extension for Visual Studio Code (versions prior to 1.132.1) allows a local attacker to load functionality from an untrusted control sphere, achieving full compromise of confidentiality, integrity, and availability. The attack requires user interaction - specifically opening a malicious workspace or project directory - making it highly relevant in developer supply-chain and social engineering scenarios such as cloning a weaponized repository. No public exploit code or CISA KEV listing has been identified at the time of analysis, but the full CIA impact and low attack complexity elevate real-world concern for development environments.
Security-feature bypass in Microsoft Visual Studio Code lets a remote attacker deliver functionality from an untrusted control sphere (CWE-829) that circumvents a built-in protection, yielding high confidentiality, integrity, and availability impact once a victim opens or interacts with attacker-supplied content. Rated CVSS 8.8 (AV:N/AC:L/PR:N/UI:R), it requires user interaction but no authentication, and Microsoft has released a fix via MSRC. There is no public exploit identified at time of analysis and it is not on the CISA KEV list.
Local code execution in Microsoft Visual Studio Code stems from a command injection flaw (CWE-77) that lets an attacker run arbitrary commands on the host with the privileges of the editor. Reported by Microsoft with a vendor patch available, the CVSS 3.1 score of 8.4 reflects full compromise of confidentiality, integrity, and availability via a local attack vector requiring no privileges or user interaction. There is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Local privilege elevation in Microsoft Visual Studio Code allows an unprivileged attacker to gain higher privileges on a host by tricking a user into triggering inclusion of functionality from an untrusted control sphere (CWE-94 code injection class). The flaw requires user interaction and local access per the CVSS vector (AV:L/UI:R), yielding full confidentiality, integrity, and availability impact at CVSS 7.8. No public exploit identified at time of analysis and the issue is not listed in CISA KEV.
Privilege escalation in Microsoft Visual Studio Code allows remote unauthenticated attackers to elevate privileges over a network when a victim performs a required interaction, due to improper input validation classified as missing authentication (CWE-306). The flaw carries a critical CVSS 9.6 score with scope change, meaning a successful attack impacts resources beyond the vulnerable component. No public exploit identified at time of analysis, but the user-interaction trigger combined with VS Code's massive developer install base makes this a notable supply-chain-adjacent risk.
Security feature bypass via path traversal in GitHub Copilot and Visual Studio Code allows a local unauthorized attacker to escape a restricted directory and reach files or resources that should be inaccessible. The flaw is tracked under CWE-22 with a CVSS 3.1 base score of 8.4 (AV:L/AC:L/PR:N/UI:N) reflecting high confidentiality, integrity, and availability impact from local exploitation. There is no public exploit identified at time of analysis and the issue is not listed in CISA KEV.
Privilege escalation in Microsoft Visual Studio Code versions 1.0.0 through 1.119.0 allows remote unauthenticated attackers to elevate privileges over a network by exploiting improper input validation (CWE-20). Microsoft has released a patched build (1.119.1) and SSVC rates technical impact as total, though EPSS remains low at 0.09% with no public exploit identified at time of analysis.
Privilege elevation in Microsoft Visual Studio Code (all releases from 1.0.0 up to but not including 1.119.1) stems from a session fixation weakness (CWE-384) that a remote, unauthenticated attacker can leverage to hijack a victim's authenticated session after the victim is lured into interacting with an attacker-supplied session identifier. The flaw carries a CVSS 8.8 rating with total confidentiality, integrity, and availability impact, but currently has no public exploit identified at time of analysis and a low EPSS score of 0.06% (18th percentile). Microsoft self-reported the issue and has shipped a fix, while CISA's SSVC framework records exploitation as 'none' and non-automatable.
Local code execution in Microsoft Visual Studio Code before 1.119.1 stems from improper neutralization of script-related HTML tags (basic XSS, CWE-80) rendered within the editor's webview surfaces, letting an attacker who tricks a user into opening crafted content run code in the victim's context. Exploitation requires user interaction (opening a malicious file/workspace) and is reported by Microsoft with a patch available; there is no public exploit identified at time of analysis, and EPSS is negligible at 0.05% (16th percentile).
Security-feature bypass in GitHub Copilot and Visual Studio (affecting Visual Studio Code builds before 1.119.1) lets a remote, unauthenticated attacker inject unneutralized special elements into a downstream component (CWE-74) to defeat a built-in protection, provided a developer is lured into a triggering action (UI:R). With CVSS 8.8 and full confidentiality/integrity/availability impact, successful exploitation could subvert Copilot/editor security controls; however there is no public exploit identified at time of analysis, EPSS is low (0.06%), and CISA SSVC records exploitation status as none.
Authenticated users can exploit a race condition in GitHub Copilot and Visual Studio Code to execute arbitrary code remotely by manipulating file state between verification and use. This vulnerability affects users with network access to these development tools and requires user interaction to trigger. No patch is currently available to address this high-severity flaw.
GitHub Copilot and Visual Studio Code are vulnerable to command injection attacks that allow unauthenticated attackers to bypass security features over the network through improper neutralization of special command elements. The vulnerability requires user interaction to exploit and could enable attackers to execute arbitrary commands with high impact on confidentiality, integrity, and availability. No patch is currently available for this issue.
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity.
Arbitrary file write in the Markdown Preview Enhanced extension for Visual Studio Code (all versions before 0.8.30) lets JavaScript already running inside a preview webview invoke the _crossnote.updateMarkdown command with an arbitrary target URI and attacker-supplied content; the extension then hands both straight to vscode.workspace.fs.writeFile, so configuration, startup, source, and build files can be overwritten within the limits of the VS Code user's operating-system privileges. Exploitation is conditional rather than standalone: remote attackers need no credentials per the CVSS PR:N vector, but the victim must open attacker-controlled Markdown or repository content with the extension active, and the attacker must first obtain a separate webview JavaScript execution path such as the .crossnote/head.html script injection or the blind command-dispatch weakness fixed in the same release. No public exploit code and no confirmed active exploitation were identified at time of analysis, and a vendor patch exists in 0.8.30, making this a moderate, conditional risk rather than a drop-everything priority.
Script injection in Markdown Preview Enhanced (a Visual Studio Code extension) before 0.8.30 lets a malicious repository execute attacker-controlled JavaScript inside the preview webview as soon as a victim opens a Markdown preview. Because the injected code runs before the React application and DOMPurify are initialized, it can reach acquireVsCodeApi() and send arbitrary messages to the extension host, giving an attacker host-level command influence (integrity impact is rated High in the assessed vector). Exploitation requires the extension to be installed, the victim to have an attacker-controlled repository on disk, and the victim to open a preview of a Markdown file in that repository - the preview itself is the trigger and no further click is needed. No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited (no CISA KEV listing); the vendor-released fix is 0.8.30, which upgrades the bundled crossnote library to 0.9.31.
A local security-feature bypass in Visual Studio Code (all builds from 1.0.0 up to but not including 1.141.1) lets a low-privileged, already-authorized local attacker violate the editor's privilege boundaries under specific, hard-to-control conditions, with the integrity impact extending beyond VS Code's own security scope. Exploitation is not remotely reachable: it requires local access on the same host (AV:L), an existing low-privilege account (PR:L), a high-complexity precondition such as a race or particular environmental state (AC:H), and a victim action inside the editor (UI:R), which substantially constrains real-world abuse. There is no public exploit identified at time of analysis, no CISA KEV listing, and the vendor has released a patch, so this should be handled as a routine moderate-severity patch priority rather than an emergency.
Information disclosure in Visual Studio Code stems from a path traversal flaw (CWE-22) that allows an attacker holding a low-privileged position and delivering crafted content to read files outside the intended workspace boundary once a victim opens that content. Versions from 1.0.0 up to but not including 1.141.1 are affected, and exploitation is not autonomous: the CVSS vector requires user interaction (UI:R) for the victim to open the malicious workspace, repository, or project folder, along with the privilege level indicated by PR:L, while impact is confined to confidentiality (C:H) with no integrity or availability effect. There is no confirmed active exploitation (CISA KEV does not list this CVE) and no public exploit code identified at time of analysis; at CVSS 6.8 this is a moderate-severity information-disclosure issue rather than a drop-everything emergency, and the vendor has published an update guide with patch availability.
Command injection in SAP Yeoman UI (app-studio-toolkit) enables an attacker to execute arbitrary OS commands with the developer's privileges by crafting a malicious workspace settings.json that sets ApplicationWizard.installationLocation to a shell payload. The command fires when the developer triggers a generator installation or uninstallation, which invokes child_process.execSync with the unsanitized value. The assessed CVSS vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) indicates local exploitation requiring user interaction, with high impact to confidentiality, integrity, and availability on the developer workstation; no confirmed active exploitation or public exploit code is identified in the provided data.
Command injection (CWE-77) in Visual Studio Code versions prior to 1.136.2 and GitHub Copilot enables a network-based attacker without authentication to trigger disclosure of sensitive information when a targeted developer interacts with specially crafted content. The attack requires high complexity (AC:H) and user interaction (UI:R), yielding a CVSS 5.3 Medium score that reflects real exploitation barriers. No public exploit code and no CISA KEV listing have been identified at time of analysis.
Path traversal in Visual Studio Code (all versions prior to 1.136.2) allows a remote unauthenticated attacker to write files outside the intended restricted directory, achieving high-integrity tampering on the victim's system over a network. The attack requires user interaction - a victim must open or process attacker-controlled content within VS Code - which limits automatability. No active exploitation has been identified; SSVC assessment confirms exploitation status as none with partial technical impact. Microsoft has released a fix in version 1.136.2.
Command injection in Visual Studio Code versions prior to 1.132.1 enables remote unauthenticated attackers to disclose sensitive information from a victim's system over a network. Exploitation requires user interaction - the victim must open or engage with attacker-controlled content such as a malicious workspace, configuration file, or repository - consistent with the CVSS UI:R metric. No public exploit code or CISA KEV listing is identified at time of analysis; a vendor-released patch (1.132.1) is available via the Microsoft Security Response Center.
Cross-site scripting in Microsoft Visual Studio Code lets an attacker who tricks a local user into opening crafted content bypass a built-in security feature and gain high-impact code execution within the editor context. The flaw (CWE-79) carries a CVSS 3.1 base score of 7.1 with a local attack vector requiring user interaction, and Microsoft has published an advisory with a fix. There is no public exploit identified at time of analysis and the CVE is not listed in CISA KEV.
Path traversal in Microsoft Visual Studio Code (all versions from 1.0.0 up to 1.128.1) enables a locally-authenticated low-privilege attacker to bypass a file-system security boundary and read files outside a restricted directory, resulting in high confidentiality impact. The vulnerability is rated CVSS 5.5 Medium and is limited to local attack vectors, requiring PR:L authenticated access. No public exploit code or active exploitation has been identified at time of analysis; EPSS stands at 0.45% and SSVC designates exploitation status as none, making this a lower-priority remediation item despite the High confidentiality impact rating.
Credential disclosure in Visual Studio Code (including GitHub Copilot integration) exposes user credentials to network-positioned attackers across all versions prior to 1.128.1. Rooted in CWE-522 (Insufficiently Protected Credentials), the flaw enables a remote unauthenticated attacker to capture credentials when a user performs a triggering action, potentially granting access to GitHub or Microsoft services. No active exploitation is confirmed (SSVC: Exploitation none; not in CISA KEV), and the EPSS score of 0.60% reflects low observed exploitation probability at time of analysis.
Security feature bypass in Microsoft Visual Studio Code allows a local unauthenticated attacker to circumvent a built-in protection mechanism through improper input validation, requiring user interaction to trigger. With CVSS 7.1 and scope-changed impact (S:C) yielding high confidentiality exposure, the flaw lets a crafted input cross VS Code's trust boundary on the local host. There is no public exploit identified at time of analysis and the vulnerability is not listed in CISA KEV.
Relative path traversal in Visual Studio Code versions prior to 1.123.1 enables unauthenticated remote attackers to tamper with files outside the intended directory boundary, producing a high integrity impact with no confidentiality or availability loss. The CVSS vector (AV:N/AC:L/PR:N/UI:R) indicates the attack requires no privileges and is low-complexity over a network, but depends on a victim interacting with attacker-controlled content. No public exploit code has been identified and this CVE is not listed in the CISA KEV catalog at time of analysis.
Information disclosure in Visual Studio Code versions 1.0.0 through 1.123.0 allows an unauthenticated remote attacker to exfiltrate sensitive information over a network by inducing user interaction. The CVSS vector (AV:N/AC:L/PR:N/UI:R/C:H) indicates that while no authentication or elevated complexity is required on the attacker's side, the victim must perform some interaction to trigger the exposure - likely opening a malicious file, workspace, or following a crafted link within the IDE environment. No public exploit code or CISA KEV listing has been identified at time of analysis, but the high confidentiality impact and zero-privilege requirement make this a meaningful risk for developer workstations handling secrets, tokens, or source code.
Cross-site scripting in Microsoft Visual Studio Code (all versions prior to 1.119.1) allows a local attacker to inject malicious scripts into VS Code's webview rendering engine, bypassing security feature protections with high confidentiality impact across component boundaries. The CVSS Scope:Changed metric (S:C) combined with C:H indicates the injected payload can escape the webview sandbox and exfiltrate data accessible to the broader VS Code/Electron process, such as environment variables, authentication tokens, or workspace file contents. No public exploit code has been identified and EPSS sits at 0.04% (13th percentile), indicating low current exploitation pressure despite the meaningful confidentiality impact.
Untrusted code execution in the Visual Studio Code Go extension lets a crafted Go workspace run attacker-controlled tooling on a developer's machine whenever the developer relies on Restricted Mode (Workspace Trust) for protection. Prior to the fix tracked as GO-2025-4249, the extension activated and launched Go tooling inside untrusted workspaces, so opening a malicious repository or folder defeated the trust boundary VS Code is designed to enforce. Exploitation requires the developer to actively open the attacker-supplied project and to depend on Restricted Mode; there is no confirmed active exploitation (not listed in CISA KEV) and no public exploit code identified at time of analysis, and EPSS is low at roughly 0.45% (37th percentile), consistent with a moderate developer-workstation risk rather than an internet-facing emergency.
Improper access control in GitHub Copilot and Visual Studio Code allows an authorized attacker to execute code over a network. Rated high severity (CVSS 8.0), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
Improper validation of generative ai output in GitHub Copilot and Visual Studio Code allows an authorized attacker to bypass a security feature locally. Rated medium severity (CVSS 5.0), this vulnerability is low attack complexity. No vendor patch available.
GitHub Workflow Updater for VS Code before 0.0.7 stored a user-provided GitHub Personal Access Token in plaintext in the editor configuration JSON on disk rather than using the VS Code SecretStorage API, so anyone with local read access to the victim's home directory could recover the token and use it under the victim's GitHub permissions. Exploitation requires that the victim previously configured a token in a vulnerable version and that the attacker already has local filesystem read access; the CVSS v3.1 score is 3.8 with a local vector, EPSS is 0.13%, and no public exploit was identified at time of analysis. Version 0.0.7 fixes this by migrating token handling to SecretStorage.
Ai command injection in Agentic AI and Visual Studio Code allows an unauthorized attacker to execute code over a network. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
Files or directories accessible to external parties in Visual Studio Code allows an unauthorized attacker to bypass a security feature locally. Rated high severity (CVSS 7.1), this vulnerability is no authentication required, low attack complexity. No vendor patch available.
Improper access control in Visual Studio Code allows an authorized attacker to elevate privileges locally. Rated medium severity (CVSS 6.8), this vulnerability is low attack complexity. No vendor patch available.
Visual Studio Code JS Debug Extension Elevation of Privilege Vulnerability. Rated high severity (CVSS 7.3), this vulnerability is low attack complexity. No vendor patch available.
Visual Studio Code Elevation of Privilege Vulnerability. Rated high severity (CVSS 7.3), this vulnerability is low attack complexity. No vendor patch available.
Visual Studio Code for Linux Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity. This Command Injection vulnerability could allow attackers to inject arbitrary commands into system command execution.
Missing authentication for critical function in Visual Studio Code extension for Arduino allows an unauthenticated attacker to perform remote code execution through network attack vector. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity.
Visual Studio Code Elevation of Privilege Vulnerability. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity.
Visual Studio Code Spoofing Vulnerability. Rated medium severity (CVSS 6.6), this vulnerability is low attack complexity.
Visual Studio Code Spoofing Vulnerability. Rated medium severity (CVSS 6.6), this vulnerability is low attack complexity.
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity.
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity. No vendor patch available.
Visual Studio Code Information Disclosure Vulnerability. Rated high severity (CVSS 7.4), this vulnerability is remotely exploitable, no authentication required, low attack complexity.
Visual Studio Code Elevation of Privilege Vulnerability. Rated high severity (CVSS 7.3), this vulnerability is low attack complexity. No vendor patch available.
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available.
Visual Studio Code Elevation of Privilege Vulnerability. Rated high severity (CVSS 7.3), this vulnerability is low attack complexity. No vendor patch available.
Visual Studio Code Spoofing Vulnerability. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
Visual Studio Code Spoofing Vulnerability. Rated medium severity (CVSS 4.3), this vulnerability is remotely exploitable, no authentication required, low attack complexity.
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity.
Visual Studio Code Elevation of Privilege Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. This Improper Privilege Management vulnerability could allow attackers to escalate privileges to gain unauthorized elevated access.
Visual Studio Code Spoofing Vulnerability. Rated medium severity (CVSS 5.5), this vulnerability is no authentication required, low attack complexity.
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity.
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity.
Microsoft Visual Studio Spoofing Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity.
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity.
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity.
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.0), this vulnerability is no authentication required.
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity.
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity.
Remote Development Extension for Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity.
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity.
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity.
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity.
Remote code execution in Markdown Preview Enhanced (a Visual Studio Code Markdown preview extension) before 0.8.29 lets a malicious repository run operating-system commands as the victim's account the moment the victim opens a Markdown file from that repository. The extension automatically evaluates repository-controlled .crossnote/config.js and .crossnote/parser.js files through vm.runInNewContext, and prototype-chain traversal escapes the Node.js host realm to reach the Function constructor and the process object - no further interaction and no module-scoped require are needed, and both the configuration-evaluation and parser-hook paths are affected. The vector requires local placement of the repository plus user interaction (opening the file), so it is not mass-exploitable over the network against a default install; there is no CISA KEV listing and no public exploit identified at time of analysis. The issue is fixed in Markdown Preview Enhanced 0.8.29, which bundles crossnote 0.9.30.
Remote code execution in Visual Studio Code (versions 1.0.0 up to but not including 1.141.1) is achievable through a path traversal flaw when a victim opens a crafted workspace, folder, or repository containing malicious pathnames that escape the intended restricted directory. The attack is unauthenticated (PR:N) but requires user interaction (UI:R), and the scope change (S:C) alongside high confidentiality, integrity, and availability impacts yields a CVSS score of 9.6. Microsoft has released a vendor patch (1.141.1); no public exploit code has been identified at time of analysis, though the severity warrants prompt patching.
Remote code execution in Visual Studio Code versions 1.0.0 through 1.141.1 allows an unauthenticated, network-positioned attacker to execute arbitrary code when a victim opens attacker-controlled content (e.g., a crafted workspace, folder, or repository), due to improper output encoding/escaping (CWE-116). Exploitation requires user interaction, and no public exploit code has been identified at time of analysis. The vendor has released a patch in version 1.141.1.
An unauthenticated, network-positioned attacker can bypass a security feature in Visual Studio Code versions 1.0.0 up to but not including 1.141.1 by getting a victim to open or interact with attacker-controlled content, resulting in high confidentiality impact (CVSS 7.4, S:C/C:H/I:N/A:N). The user-interaction requirement (UI:R) is the primary limiting factor - the flaw cannot be triggered fully passively and no privileges or local access are needed once the victim interacts. Neither KEV confirmation nor public exploit code has been identified at time of analysis, so this is a moderate-priority patching item rather than an emergency, though the scope-changed, high-confidentiality rating keeps it above routine maintenance.
Command injection in Visual Studio Code 1.0.0 through 1.141.0 allows an unauthenticated remote attacker to execute arbitrary code in the context of the editor when a developer opens attacker-controlled content such as a malicious workspace, folder, repository, or project configuration file. Exploitation depends on user interaction (a victim must open the crafted project), but is otherwise low-complexity with high confidentiality, integrity, and availability impact; no public exploit code has been identified at the time of analysis. Microsoft has released a vendor fix in Visual Studio Code 1.141.1.
Missing authorization in Visual Studio Code lets a local attacker bypass a security feature once the victim opens attacker-controlled content, such as a crafted workspace, folder, or file, producing high confidentiality, integrity, and availability impact (CVSS 3.1 base 7.8, AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). No pre-existing privileges or authentication are required, but exploitation demands local delivery of the malicious content plus mandatory user interaction, which rules out remote, unattended, or automated mass exploitation. No public exploit code has been identified at time of analysis, and the specific security feature being bypassed is not detailed in the available data and should be confirmed against the Microsoft MSRC advisory.
Improper resolution of path equivalence (CWE-41) in Visual Studio Code allows an unauthenticated local attacker to bypass a security feature, likely Workspace Trust or restricted mode, by convincing a victim to open and interact with a crafted workspace or folder. The vulnerability requires user interaction and high attack complexity, and while it has a CVSS score of 7.7 (High), it is a moderate-priority developer-workstation issue rather than an internet-facing emergency. No public exploit code has been identified at time of analysis, and the exact affected versions should be confirmed via the linked Microsoft advisory.
Information disclosure in Visual Studio Code allows an unauthenticated remote attacker to exfiltrate sensitive data via a crafted file or workspace that triggers incorrect name or reference resolution (CWE-706). Affected versions span 1.0.0 through all releases before 1.136.2. The scope change (S:C) in the CVSS vector indicates the confidentiality impact reaches beyond the VS Code process itself - potentially exposing system files, environment variables, or workspace secrets to a remote origin. No public exploit code or KEV listing is identified at time of analysis, but the broad affected version range and VS Code's developer-centric user base make this a meaningful supply-chain adjacent risk.
Insufficient protection of stored or transmitted credentials in GitHub Copilot and Visual Studio Code before 1.136.2 allows a network-positioned attacker to disclose sensitive information, including authentication tokens, with a CVSS base score of 7.5 (AV:N/AC:L/PR:N/UI:N/C:H/I:N/A:N). Microsoft (secure@microsoft.com) is the assigning CNA and a vendored patch is available, but CISA SSVC rates exploitation as 'none' and automatable as 'no', and EPSS is only 0.62% (47th percentile), indicating elevated theoretical severity without observed attacker activity. No public exploit code has been identified at time of analysis.
Security feature bypass in Visual Studio Code before 1.136.2 allows a remote, unauthenticated attacker to circumvent a protection mechanism via a failing-open (CWE-636) code path, resulting in high confidentiality impact and limited integrity impact across a changed scope. The vulnerability is reachable over the network with low complexity but requires user interaction, suggesting an attacker must induce the victim to open a crafted workspace, file, or URI. No public exploit code and no CISA KEV listing have been identified at time of analysis, though Microsoft has released a patch.
Security feature bypass in Visual Studio Code (versions 1.0.0 through below 1.136.2) allows a remote unauthenticated attacker to circumvent a protective security control via an interpretation conflict in the editor's processing pipeline. The vulnerability requires user interaction (UI:R) - a victim must open or interact with attacker-influenced content - after which the scope change (S:C) and high confidentiality impact suggest sensitive host data or credentials may be exfiltrated beyond the process boundary. No public exploit or CISA KEV listing has been identified at time of analysis.
Security-feature bypass in Microsoft Visual Studio Code before 1.136.2 lets a remote, unauthenticated attacker defeat a protection mechanism when a user is lured into interacting with malicious content (UI:R). Rooted in an incomplete comparison that omits required factors (CWE-693), the flaw carries a scope-changed CVSS 9.6 with full confidentiality, integrity, and availability impact, consistent with a trust/security-control bypass that can extend beyond the editor's initial boundary. A vendor patch exists; no public exploit is identified at time of analysis.
Server-side request forgery in Visual Studio Code prior to 1.136.2 allows a remote unauthenticated attacker to bypass security features and force VS Code to issue HTTP requests to internal or otherwise restricted network resources on the victim's behalf. Exploitation requires user interaction - a developer must open or trigger attacker-controlled content within VS Code - after which the editor acts as a request proxy, crossing trust boundaries (S:C) to reach endpoints inaccessible from the attacker's network position. No public exploit code or active CISA KEV listing has been identified at time of analysis; however, developers are high-value targets due to their typical privileged network access to internal infrastructure.
HTTP request smuggling in Visual Studio Code (versions 1.0.0 through 1.136.2) enables unauthenticated network attackers to bypass security controls through inconsistent interpretation of HTTP request boundaries. The CVSS scope change (S:C) signals that impact extends beyond the editor itself - smuggled requests can affect back-end services or proxies that VS Code communicates with, resulting in high confidentiality exposure. No public exploit code or CISA KEV listing has been identified at time of analysis, but the network-accessible, unauthenticated nature of the attack surface warrants prompt patching.
Authorization bypass in Visual Studio Code versions 1.0.0 through 1.136.1 allows an unauthenticated network attacker to circumvent a security feature via a user-controlled key (CWE-639), with user interaction required to trigger exploitation. The CVSS 8.8 score reflects full impact across confidentiality, integrity, and availability (C:H/I:H/A:H), indicating potential complete compromise of the affected VS Code instance. A vendor-released patch is available in version 1.136.2 per the Microsoft Security Response Center; no public exploit code or CISA KEV listing has been identified at time of analysis.
Path traversal in Visual Studio Code versions prior to 1.136.2 enables a remote unauthenticated attacker - contingent on user interaction - to escape the editor's restricted directory boundary and read sensitive files from the host system, effectively bypassing a security feature such as workspace trust or sandbox isolation. The vulnerability carries a CVSS 7.4 with Scope:Changed and C:H, reflecting that the impact crosses from VS Code's own context into broader host file system access. No public exploit code or CISA KEV listing has been identified at time of analysis.
Security feature bypass in Visual Studio Code before 1.136.2 allows a local attacker to circumvent an input-validation blocklist (CWE-184), resulting in high confidentiality, integrity, and availability impact. The vulnerability requires user interaction - most plausibly opening a crafted workspace or file - but no elevated privileges. Microsoft shipped a vendor patch capping affected versions below 1.136.2; no public exploit or CISA KEV listing has been identified at time of analysis.
Remote code execution in Microsoft Visual Studio Code allows a network-based attacker to inject and execute arbitrary code on a victim's machine with no prior authentication, provided the victim performs a user interaction - such as opening a malicious workspace, file, or URI. Classified under CWE-94 (Code Injection), the vulnerability carries a CVSS base score of 8.8, reflecting high impact across confidentiality, integrity, and availability. No public exploit code or CISA KEV listing was identified at the time of analysis, but the attack complexity is rated Low, making reliable exploitation straightforward once a victim is lured.
OS command injection in GitHub Copilot and Visual Studio Code enables a local unauthorized attacker to escalate privileges on the affected developer workstation, achieving full High impact across confidentiality, integrity, and availability. The CWE-78 root cause indicates that attacker-influenced input containing shell metacharacters is improperly incorporated into OS-level command execution within one or both products, triggering upon a user action such as opening a malicious file or repository. No public exploit code has been identified and this vulnerability has not been confirmed actively exploited by CISA KEV at time of analysis; however, the local privilege escalation path on widely deployed developer tooling represents a meaningful risk in supply chain and social engineering scenarios.
OS command injection in Visual Studio Code exposes victims to remote code execution when they interact with attacker-controlled content, such as a malicious workspace, repository, or file. The vulnerability (CWE-78) stems from improper neutralization of shell metacharacters in input passed to OS-level command execution routines, giving an unauthenticated network attacker the ability to run arbitrary commands with the privileges of the VS Code process. No active exploitation has been confirmed by CISA KEV, and no public proof-of-concept is referenced at time of analysis.
Fail-open security logic in Visual Studio Code permits network-based security feature bypass by an unauthenticated attacker who can induce user interaction. The root cause is CWE-636: when the application encounters an error or edge condition in a security enforcement path, it defaults to granting rather than denying access, neutralizing the intended control. With a CVSS score of 8.2 and a scope-changed vector (S:C) paired with high confidentiality impact, successful exploitation could expose data or capabilities beyond the direct VS Code process boundary. No public exploit code or CISA KEV listing has been identified at time of analysis.
Local security feature bypass in Visual Studio Code allows an attacker with local access to circumvent an authorization control, achieving high-impact compromise of confidentiality, integrity, and availability on the affected system. The vulnerability (CWE-693, Protection Mechanism Failure) is exploitable locally without elevated privileges but requires user interaction, making social engineering or physical access the likely delivery path. No public exploit code or active exploitation has been identified at time of analysis.
Remote code execution in Visual Studio Code (versions 1.0.0 through 1.132.0) is enabled by a missing authorization check (CWE-862) on a network-accessible code path, allowing an unauthenticated network attacker to execute arbitrary code on a victim's machine with high impact across confidentiality, integrity, and availability. Exploitation requires user interaction (CVSS UI:R), meaning the victim must engage with attacker-controlled content. A vendor-released patch is available in version 1.132.1; no public exploit code or CISA KEV listing is confirmed at time of analysis.
Security feature bypass in Visual Studio Code (versions 1.0.0 through 1.132.1) exploits CWE-639, where authorization decisions rely on attacker-controllable keys, allowing a local attacker to circumvent an intended access control with high impact across confidentiality, integrity, and availability. The attack requires no elevated attacker privileges but does require a legitimate VS Code user to interact with the manipulated environment, pointing to shared-workstation or social-engineering delivery paths. No public exploit code has been identified and this CVE is absent from the CISA KEV catalog at time of analysis; a vendor-released patch is available at version 1.132.1.
Security feature bypass in the Python extension for Visual Studio Code (versions prior to 1.132.1) allows a local attacker to load functionality from an untrusted control sphere, achieving full compromise of confidentiality, integrity, and availability. The attack requires user interaction - specifically opening a malicious workspace or project directory - making it highly relevant in developer supply-chain and social engineering scenarios such as cloning a weaponized repository. No public exploit code or CISA KEV listing has been identified at the time of analysis, but the full CIA impact and low attack complexity elevate real-world concern for development environments.
Security-feature bypass in Microsoft Visual Studio Code lets a remote attacker deliver functionality from an untrusted control sphere (CWE-829) that circumvents a built-in protection, yielding high confidentiality, integrity, and availability impact once a victim opens or interacts with attacker-supplied content. Rated CVSS 8.8 (AV:N/AC:L/PR:N/UI:R), it requires user interaction but no authentication, and Microsoft has released a fix via MSRC. There is no public exploit identified at time of analysis and it is not on the CISA KEV list.
Local code execution in Microsoft Visual Studio Code stems from a command injection flaw (CWE-77) that lets an attacker run arbitrary commands on the host with the privileges of the editor. Reported by Microsoft with a vendor patch available, the CVSS 3.1 score of 8.4 reflects full compromise of confidentiality, integrity, and availability via a local attack vector requiring no privileges or user interaction. There is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Local privilege elevation in Microsoft Visual Studio Code allows an unprivileged attacker to gain higher privileges on a host by tricking a user into triggering inclusion of functionality from an untrusted control sphere (CWE-94 code injection class). The flaw requires user interaction and local access per the CVSS vector (AV:L/UI:R), yielding full confidentiality, integrity, and availability impact at CVSS 7.8. No public exploit identified at time of analysis and the issue is not listed in CISA KEV.
Privilege escalation in Microsoft Visual Studio Code allows remote unauthenticated attackers to elevate privileges over a network when a victim performs a required interaction, due to improper input validation classified as missing authentication (CWE-306). The flaw carries a critical CVSS 9.6 score with scope change, meaning a successful attack impacts resources beyond the vulnerable component. No public exploit identified at time of analysis, but the user-interaction trigger combined with VS Code's massive developer install base makes this a notable supply-chain-adjacent risk.
Security feature bypass via path traversal in GitHub Copilot and Visual Studio Code allows a local unauthorized attacker to escape a restricted directory and reach files or resources that should be inaccessible. The flaw is tracked under CWE-22 with a CVSS 3.1 base score of 8.4 (AV:L/AC:L/PR:N/UI:N) reflecting high confidentiality, integrity, and availability impact from local exploitation. There is no public exploit identified at time of analysis and the issue is not listed in CISA KEV.
Privilege escalation in Microsoft Visual Studio Code versions 1.0.0 through 1.119.0 allows remote unauthenticated attackers to elevate privileges over a network by exploiting improper input validation (CWE-20). Microsoft has released a patched build (1.119.1) and SSVC rates technical impact as total, though EPSS remains low at 0.09% with no public exploit identified at time of analysis.
Privilege elevation in Microsoft Visual Studio Code (all releases from 1.0.0 up to but not including 1.119.1) stems from a session fixation weakness (CWE-384) that a remote, unauthenticated attacker can leverage to hijack a victim's authenticated session after the victim is lured into interacting with an attacker-supplied session identifier. The flaw carries a CVSS 8.8 rating with total confidentiality, integrity, and availability impact, but currently has no public exploit identified at time of analysis and a low EPSS score of 0.06% (18th percentile). Microsoft self-reported the issue and has shipped a fix, while CISA's SSVC framework records exploitation as 'none' and non-automatable.
Local code execution in Microsoft Visual Studio Code before 1.119.1 stems from improper neutralization of script-related HTML tags (basic XSS, CWE-80) rendered within the editor's webview surfaces, letting an attacker who tricks a user into opening crafted content run code in the victim's context. Exploitation requires user interaction (opening a malicious file/workspace) and is reported by Microsoft with a patch available; there is no public exploit identified at time of analysis, and EPSS is negligible at 0.05% (16th percentile).
Security-feature bypass in GitHub Copilot and Visual Studio (affecting Visual Studio Code builds before 1.119.1) lets a remote, unauthenticated attacker inject unneutralized special elements into a downstream component (CWE-74) to defeat a built-in protection, provided a developer is lured into a triggering action (UI:R). With CVSS 8.8 and full confidentiality/integrity/availability impact, successful exploitation could subvert Copilot/editor security controls; however there is no public exploit identified at time of analysis, EPSS is low (0.06%), and CISA SSVC records exploitation status as none.
Authenticated users can exploit a race condition in GitHub Copilot and Visual Studio Code to execute arbitrary code remotely by manipulating file state between verification and use. This vulnerability affects users with network access to these development tools and requires user interaction to trigger. No patch is currently available to address this high-severity flaw.
GitHub Copilot and Visual Studio Code are vulnerable to command injection attacks that allow unauthenticated attackers to bypass security features over the network through improper neutralization of special command elements. The vulnerability requires user interaction to exploit and could enable attackers to execute arbitrary commands with high impact on confidentiality, integrity, and availability. No patch is currently available for this issue.
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity.
Arbitrary file write in the Markdown Preview Enhanced extension for Visual Studio Code (all versions before 0.8.30) lets JavaScript already running inside a preview webview invoke the _crossnote.updateMarkdown command with an arbitrary target URI and attacker-supplied content; the extension then hands both straight to vscode.workspace.fs.writeFile, so configuration, startup, source, and build files can be overwritten within the limits of the VS Code user's operating-system privileges. Exploitation is conditional rather than standalone: remote attackers need no credentials per the CVSS PR:N vector, but the victim must open attacker-controlled Markdown or repository content with the extension active, and the attacker must first obtain a separate webview JavaScript execution path such as the .crossnote/head.html script injection or the blind command-dispatch weakness fixed in the same release. No public exploit code and no confirmed active exploitation were identified at time of analysis, and a vendor patch exists in 0.8.30, making this a moderate, conditional risk rather than a drop-everything priority.
Script injection in Markdown Preview Enhanced (a Visual Studio Code extension) before 0.8.30 lets a malicious repository execute attacker-controlled JavaScript inside the preview webview as soon as a victim opens a Markdown preview. Because the injected code runs before the React application and DOMPurify are initialized, it can reach acquireVsCodeApi() and send arbitrary messages to the extension host, giving an attacker host-level command influence (integrity impact is rated High in the assessed vector). Exploitation requires the extension to be installed, the victim to have an attacker-controlled repository on disk, and the victim to open a preview of a Markdown file in that repository - the preview itself is the trigger and no further click is needed. No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited (no CISA KEV listing); the vendor-released fix is 0.8.30, which upgrades the bundled crossnote library to 0.9.31.
A local security-feature bypass in Visual Studio Code (all builds from 1.0.0 up to but not including 1.141.1) lets a low-privileged, already-authorized local attacker violate the editor's privilege boundaries under specific, hard-to-control conditions, with the integrity impact extending beyond VS Code's own security scope. Exploitation is not remotely reachable: it requires local access on the same host (AV:L), an existing low-privilege account (PR:L), a high-complexity precondition such as a race or particular environmental state (AC:H), and a victim action inside the editor (UI:R), which substantially constrains real-world abuse. There is no public exploit identified at time of analysis, no CISA KEV listing, and the vendor has released a patch, so this should be handled as a routine moderate-severity patch priority rather than an emergency.
Information disclosure in Visual Studio Code stems from a path traversal flaw (CWE-22) that allows an attacker holding a low-privileged position and delivering crafted content to read files outside the intended workspace boundary once a victim opens that content. Versions from 1.0.0 up to but not including 1.141.1 are affected, and exploitation is not autonomous: the CVSS vector requires user interaction (UI:R) for the victim to open the malicious workspace, repository, or project folder, along with the privilege level indicated by PR:L, while impact is confined to confidentiality (C:H) with no integrity or availability effect. There is no confirmed active exploitation (CISA KEV does not list this CVE) and no public exploit code identified at time of analysis; at CVSS 6.8 this is a moderate-severity information-disclosure issue rather than a drop-everything emergency, and the vendor has published an update guide with patch availability.
Command injection in SAP Yeoman UI (app-studio-toolkit) enables an attacker to execute arbitrary OS commands with the developer's privileges by crafting a malicious workspace settings.json that sets ApplicationWizard.installationLocation to a shell payload. The command fires when the developer triggers a generator installation or uninstallation, which invokes child_process.execSync with the unsanitized value. The assessed CVSS vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) indicates local exploitation requiring user interaction, with high impact to confidentiality, integrity, and availability on the developer workstation; no confirmed active exploitation or public exploit code is identified in the provided data.
Command injection (CWE-77) in Visual Studio Code versions prior to 1.136.2 and GitHub Copilot enables a network-based attacker without authentication to trigger disclosure of sensitive information when a targeted developer interacts with specially crafted content. The attack requires high complexity (AC:H) and user interaction (UI:R), yielding a CVSS 5.3 Medium score that reflects real exploitation barriers. No public exploit code and no CISA KEV listing have been identified at time of analysis.
Path traversal in Visual Studio Code (all versions prior to 1.136.2) allows a remote unauthenticated attacker to write files outside the intended restricted directory, achieving high-integrity tampering on the victim's system over a network. The attack requires user interaction - a victim must open or process attacker-controlled content within VS Code - which limits automatability. No active exploitation has been identified; SSVC assessment confirms exploitation status as none with partial technical impact. Microsoft has released a fix in version 1.136.2.
Command injection in Visual Studio Code versions prior to 1.132.1 enables remote unauthenticated attackers to disclose sensitive information from a victim's system over a network. Exploitation requires user interaction - the victim must open or engage with attacker-controlled content such as a malicious workspace, configuration file, or repository - consistent with the CVSS UI:R metric. No public exploit code or CISA KEV listing is identified at time of analysis; a vendor-released patch (1.132.1) is available via the Microsoft Security Response Center.
Cross-site scripting in Microsoft Visual Studio Code lets an attacker who tricks a local user into opening crafted content bypass a built-in security feature and gain high-impact code execution within the editor context. The flaw (CWE-79) carries a CVSS 3.1 base score of 7.1 with a local attack vector requiring user interaction, and Microsoft has published an advisory with a fix. There is no public exploit identified at time of analysis and the CVE is not listed in CISA KEV.
Path traversal in Microsoft Visual Studio Code (all versions from 1.0.0 up to 1.128.1) enables a locally-authenticated low-privilege attacker to bypass a file-system security boundary and read files outside a restricted directory, resulting in high confidentiality impact. The vulnerability is rated CVSS 5.5 Medium and is limited to local attack vectors, requiring PR:L authenticated access. No public exploit code or active exploitation has been identified at time of analysis; EPSS stands at 0.45% and SSVC designates exploitation status as none, making this a lower-priority remediation item despite the High confidentiality impact rating.
Credential disclosure in Visual Studio Code (including GitHub Copilot integration) exposes user credentials to network-positioned attackers across all versions prior to 1.128.1. Rooted in CWE-522 (Insufficiently Protected Credentials), the flaw enables a remote unauthenticated attacker to capture credentials when a user performs a triggering action, potentially granting access to GitHub or Microsoft services. No active exploitation is confirmed (SSVC: Exploitation none; not in CISA KEV), and the EPSS score of 0.60% reflects low observed exploitation probability at time of analysis.
Security feature bypass in Microsoft Visual Studio Code allows a local unauthenticated attacker to circumvent a built-in protection mechanism through improper input validation, requiring user interaction to trigger. With CVSS 7.1 and scope-changed impact (S:C) yielding high confidentiality exposure, the flaw lets a crafted input cross VS Code's trust boundary on the local host. There is no public exploit identified at time of analysis and the vulnerability is not listed in CISA KEV.
Relative path traversal in Visual Studio Code versions prior to 1.123.1 enables unauthenticated remote attackers to tamper with files outside the intended directory boundary, producing a high integrity impact with no confidentiality or availability loss. The CVSS vector (AV:N/AC:L/PR:N/UI:R) indicates the attack requires no privileges and is low-complexity over a network, but depends on a victim interacting with attacker-controlled content. No public exploit code has been identified and this CVE is not listed in the CISA KEV catalog at time of analysis.
Information disclosure in Visual Studio Code versions 1.0.0 through 1.123.0 allows an unauthenticated remote attacker to exfiltrate sensitive information over a network by inducing user interaction. The CVSS vector (AV:N/AC:L/PR:N/UI:R/C:H) indicates that while no authentication or elevated complexity is required on the attacker's side, the victim must perform some interaction to trigger the exposure - likely opening a malicious file, workspace, or following a crafted link within the IDE environment. No public exploit code or CISA KEV listing has been identified at time of analysis, but the high confidentiality impact and zero-privilege requirement make this a meaningful risk for developer workstations handling secrets, tokens, or source code.
Cross-site scripting in Microsoft Visual Studio Code (all versions prior to 1.119.1) allows a local attacker to inject malicious scripts into VS Code's webview rendering engine, bypassing security feature protections with high confidentiality impact across component boundaries. The CVSS Scope:Changed metric (S:C) combined with C:H indicates the injected payload can escape the webview sandbox and exfiltrate data accessible to the broader VS Code/Electron process, such as environment variables, authentication tokens, or workspace file contents. No public exploit code has been identified and EPSS sits at 0.04% (13th percentile), indicating low current exploitation pressure despite the meaningful confidentiality impact.
Untrusted code execution in the Visual Studio Code Go extension lets a crafted Go workspace run attacker-controlled tooling on a developer's machine whenever the developer relies on Restricted Mode (Workspace Trust) for protection. Prior to the fix tracked as GO-2025-4249, the extension activated and launched Go tooling inside untrusted workspaces, so opening a malicious repository or folder defeated the trust boundary VS Code is designed to enforce. Exploitation requires the developer to actively open the attacker-supplied project and to depend on Restricted Mode; there is no confirmed active exploitation (not listed in CISA KEV) and no public exploit code identified at time of analysis, and EPSS is low at roughly 0.45% (37th percentile), consistent with a moderate developer-workstation risk rather than an internet-facing emergency.
Improper access control in GitHub Copilot and Visual Studio Code allows an authorized attacker to execute code over a network. Rated high severity (CVSS 8.0), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
Improper validation of generative ai output in GitHub Copilot and Visual Studio Code allows an authorized attacker to bypass a security feature locally. Rated medium severity (CVSS 5.0), this vulnerability is low attack complexity. No vendor patch available.
GitHub Workflow Updater for VS Code before 0.0.7 stored a user-provided GitHub Personal Access Token in plaintext in the editor configuration JSON on disk rather than using the VS Code SecretStorage API, so anyone with local read access to the victim's home directory could recover the token and use it under the victim's GitHub permissions. Exploitation requires that the victim previously configured a token in a vulnerable version and that the attacker already has local filesystem read access; the CVSS v3.1 score is 3.8 with a local vector, EPSS is 0.13%, and no public exploit was identified at time of analysis. Version 0.0.7 fixes this by migrating token handling to SecretStorage.
Ai command injection in Agentic AI and Visual Studio Code allows an unauthorized attacker to execute code over a network. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
Files or directories accessible to external parties in Visual Studio Code allows an unauthorized attacker to bypass a security feature locally. Rated high severity (CVSS 7.1), this vulnerability is no authentication required, low attack complexity. No vendor patch available.
Improper access control in Visual Studio Code allows an authorized attacker to elevate privileges locally. Rated medium severity (CVSS 6.8), this vulnerability is low attack complexity. No vendor patch available.
Visual Studio Code JS Debug Extension Elevation of Privilege Vulnerability. Rated high severity (CVSS 7.3), this vulnerability is low attack complexity. No vendor patch available.
Visual Studio Code Elevation of Privilege Vulnerability. Rated high severity (CVSS 7.3), this vulnerability is low attack complexity. No vendor patch available.
Visual Studio Code for Linux Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity. This Command Injection vulnerability could allow attackers to inject arbitrary commands into system command execution.
Missing authentication for critical function in Visual Studio Code extension for Arduino allows an unauthenticated attacker to perform remote code execution through network attack vector. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity.
Visual Studio Code Elevation of Privilege Vulnerability. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity.
Visual Studio Code Spoofing Vulnerability. Rated medium severity (CVSS 6.6), this vulnerability is low attack complexity.
Visual Studio Code Spoofing Vulnerability. Rated medium severity (CVSS 6.6), this vulnerability is low attack complexity.
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity.
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity. No vendor patch available.
Visual Studio Code Information Disclosure Vulnerability. Rated high severity (CVSS 7.4), this vulnerability is remotely exploitable, no authentication required, low attack complexity.
Visual Studio Code Elevation of Privilege Vulnerability. Rated high severity (CVSS 7.3), this vulnerability is low attack complexity. No vendor patch available.
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available.
Visual Studio Code Elevation of Privilege Vulnerability. Rated high severity (CVSS 7.3), this vulnerability is low attack complexity. No vendor patch available.
Visual Studio Code Spoofing Vulnerability. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
Visual Studio Code Spoofing Vulnerability. Rated medium severity (CVSS 4.3), this vulnerability is remotely exploitable, no authentication required, low attack complexity.
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity.
Visual Studio Code Elevation of Privilege Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. This Improper Privilege Management vulnerability could allow attackers to escalate privileges to gain unauthorized elevated access.
Visual Studio Code Spoofing Vulnerability. Rated medium severity (CVSS 5.5), this vulnerability is no authentication required, low attack complexity.
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity.
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity.
Microsoft Visual Studio Spoofing Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity.
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity.
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity.
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.0), this vulnerability is no authentication required.
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity.
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity.
Remote Development Extension for Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity.
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity.
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity.
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity.