Visual Studio Code EUVD-2026-99035

Exploitation requires a victim running a vulnerable Visual Studio Code version (1.0.0 up to but not including 1.141.1) to open attacker-controlled content - such as a malicious workspace, repository, or project folder - that contains the path-traversal payload (UI:R). The CVSS vector's PR:L indicates some authorization/privilege is required, so this is not a fully unauthenticated drive-by. Limiting factors: the mandatory user-interaction step (the attacker cannot trigger it autonomously), the required privilege level, and the fact that only pre-1.141.1 builds are affected. Impact is confined to confidentiality (file/information disclosure); there is no integrity or availability impact.

This is a moderate-severity information-disclosure flaw (CVSS 6.8) rather than a top-priority, drop-everything issue. The CVSS vector (AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:N/A:N) shows a network-reachable path traversal that nonetheless requires BOTH some level of authorization (PR:L) AND victim user interaction (UI:R), which materially limits mass or automated exploitation. Impact is confidentiality-only (C:H, I:N, A:N) with a changed scope (S:C), meaning disclosed data can reach beyond the originally intended security boundary. No EPSS score, no CISA KEV listing, and no public POC were provided, so there is no public exploit identified at time of analysis and no evidence of active exploitation - the signals are internally consistent (moderate base score, interaction-gated, no exploitation telemetry) and point to a patch-on-normal-cycle priority. Note the tension between AV:N and the real-world trigger: 'network' here reflects that exploitation hinges on a victim opening attacker-controlled remote content (e.g., a malicious workspace/repository), not a server listening on a port - defenders should weigh this as a client-side lure risk, not a remotely sprayable service bug.

An attacker crafts a malicious workspace, repository, or project folder containing path-traversal sequences and lures a developer into opening it in a vulnerable Visual Studio Code build (below 1.141.1). When the victim opens the content, VS Code resolves the manipulated pathname outside the intended restricted directory and discloses the contents of sensitive local files to the attacker over the network. No public exploit code was identified at time of analysis, and exploitation depends on the victim's interaction.