CVE-2026-47287: Visual Studio Code Path Traversal – File Tampering Vulnerability

Technical summary

CVE-2026-47287 is a relative path traversal vulnerability (CWE-23) in Visual Studio Code that enables unauthorized file tampering over network vectors. The vulnerability has a CVSS 3.1 score of 6.5 (Medium severity) with the following characteristics: network-based attack vector, low complexity, no privilege requirements, and user interaction needed. The impact is limited to integrity—attackers cannot achieve confidentiality or availability breaches. The vulnerability stems from insufficient validation of relative path constructs, which can be exploited to write or modify files outside the intended directory scope.

Business impact

For development teams and organizations that rely on Visual Studio Code, this vulnerability poses a moderate but concrete risk of supply chain and development environment contamination. A successful attack could result in injection of malicious code into development projects, compromised build artifacts, or corruption of configuration files. The requirement for user interaction—such as opening a specially crafted project or following an attacker-supplied link—provides a window for social engineering attacks. Teams with shared development environments or CI/CD pipelines integrated with untrusted project sources face elevated exposure.

Affected systems

The vulnerability affects Visual Studio Code across all platforms where it is deployed. The CVSS vector specifies no special software or hardware requirements beyond the application itself. Users running any version of Visual Studio Code that does not include the patch are potentially affected. The vulnerability is network-accessible, meaning exploitation does not require local system access.

Exploitability

Exploitability is moderate. An attacker must craft a malicious project, file, or network request that triggers Visual Studio Code's path traversal logic, and must convince a user to interact with it—for example, by opening a project or clicking a link. No zero-click exploitation is possible; user interaction is mandatory. The attack does not require prior authentication or elevated privileges. Given that developers commonly clone repositories and open projects from varied sources, the social engineering component is plausible in real-world scenarios.

Remediation

Users should update Visual Studio Code to the latest patched version as specified in Microsoft's advisory. Verify the exact patch version against the official Microsoft Visual Studio Code release notes, as version numbers may vary by update channel. No workarounds are documented at this time. Organizations should prioritize patching development machines and shared development servers.

Patch guidance

Check Microsoft's official Visual Studio Code security advisory and release notes for the specific patched version addressing CVE-2026-47287. Visual Studio Code typically offers automatic updates; ensure this feature is enabled. If you manage multiple instances, verify the patch version in each environment. Test the update in a non-critical environment first if your development workflow is tightly integrated with Visual Studio Code extensions or configurations.

Detection guidance

Monitor for suspicious file creation or modification activity in directories where Visual Studio Code is installed or where projects are stored. Look for unexpected relative path constructs in project files, build scripts, or configuration data. Audit project directories for files with modification timestamps that predate user actions. Check Visual Studio Code logs for errors or warnings related to file access. Network detection is limited without deep packet inspection, but monitor for unusual HTTP/HTTPS traffic to development machines from external sources combined with subsequent local file activity.

Why prioritize this

While this vulnerability requires user interaction and does not affect confidentiality, the integrity impact combined with network exploitability and the ubiquity of Visual Studio Code in development environments warrants timely patching. Development machines are often used to build and sign artifacts that propagate downstream; compromising them can affect the security posture of entire products. The moderate CVSS score should not be interpreted as low urgency for development-focused organizations.

Risk score, explained

The CVSS 3.1 score of 6.5 (Medium) reflects: network-based attack surface (AV:N), low attack complexity requiring no special conditions (AC:L), no requirement for authentication or privilege escalation (PR:N/UI:R), scoped to the attacked component (S:U), high integrity impact (I:H), and no confidentiality or availability impact (C:N/A:N). The Medium severity is appropriate because integrity compromise of development files is serious but mitigated by the requirement for user interaction and the absence of confidentiality or availability effects.

Frequently asked questions