CVE-2026-45482: GitHub Copilot Path Traversal Vulnerability

CVE-2026-45482 Overview

CVE-2026-45482 is a path traversal vulnerability affecting GitHub Copilot and Visual Studio Code. The flaw stems from improper limitation of a pathname to a restricted directory [CWE-22]. An unauthorized local attacker can leverage this weakness to bypass a security feature within the affected components. Microsoft published the advisory through MSRC and assigned the issue a CVSS 3.1 base score of 8.4. The attack vector is local, requires no privileges, and needs no user interaction, while affecting confidentiality, integrity, and availability at high impact.

Critical Impact

A local attacker can bypass security controls in GitHub Copilot and Visual Studio Code by manipulating pathnames, leading to high-impact compromise of confidentiality, integrity, and availability.

Affected Products

• GitHub Copilot
• Visual Studio Code

Discovery Timeline

• 2026-06-09 - CVE-2026-45482 published to the National Vulnerability Database
• 2026-06-09 - Last updated in NVD database

Technical Details for CVE-2026-45482

Vulnerability Analysis

The vulnerability resides in how GitHub Copilot and Visual Studio Code validate file paths before performing file system operations. The components fail to properly restrict pathnames to an intended directory. An attacker can craft input containing traversal sequences such as ../ to escape the expected boundary. This bypass undermines a security feature that would normally prevent access to files outside the permitted scope.

The weakness maps to CWE-22, Improper Limitation of a Pathname to a Restricted Directory. Successful exploitation gives the attacker the ability to read, write, or otherwise interact with files outside the intended directory tree. Because Copilot and Visual Studio Code routinely handle workspace files, extensions, and AI-generated content, the abuse surface includes developer credentials, source code, and configuration files. The EPSS data lists a probability of 0.068% with a 21.026 percentile as of 2026-06-11.

Root Cause

The root cause is insufficient sanitization and canonicalization of file path inputs handled by Copilot and Visual Studio Code logic. Path components are accepted without enforcing that the resolved path remains under the authorized root directory.

Attack Vector

Exploitation requires local access, but no authentication and no user interaction. A malicious workspace, repository, or extension content can supply crafted paths that the vulnerable code resolves outside the restricted directory. The attacker leverages this to bypass the intended security boundary. See the Microsoft Security Update CVE-2026-45482 advisory for vendor-specific technical context.

// No verified proof-of-concept code is available.
// Refer to the MSRC advisory for vendor technical details.

Detection Methods for CVE-2026-45482

Indicators of Compromise

• File access events from the Visual Studio Code process targeting paths that resolve outside the active workspace directory.
• Presence of path components such as ..\ or ../ in arguments passed to Copilot or Visual Studio Code extension APIs.
• Unexpected reads of sensitive files (for example, .ssh, .aws, .env) by the editor process shortly after opening untrusted projects.

Detection Strategies

• Hunt for editor or Copilot child processes that access files outside the user's workspace root using endpoint telemetry.
• Correlate Visual Studio Code extension installation events with subsequent anomalous file access patterns.
• Apply rules that flag path traversal sequences inside files loaded by the editor, including workspace settings and task definitions.

Monitoring Recommendations

• Enable file integrity monitoring on developer credential stores and configuration directories.
• Forward Visual Studio Code and Copilot process telemetry to a centralized analytics platform for behavioral baselining.
• Track installation of new Copilot or Visual Studio Code extensions and review their file system reach.

How to Mitigate CVE-2026-45482

Immediate Actions Required

• Apply the security updates referenced in the Microsoft Security Update CVE-2026-45482 advisory to all developer endpoints.
• Inventory installed versions of Visual Studio Code and GitHub Copilot across the environment and prioritize patching for systems handling sensitive code.
• Restrict opening of untrusted workspaces and repositories until patched versions are deployed.

Patch Information

Microsoft has published guidance and fixes through the MSRC update guide entry for CVE-2026-45482. Administrators should consult the advisory for the exact fixed versions of Visual Studio Code and GitHub Copilot components and deploy them through standard software distribution channels.

Workarounds

• Use Visual Studio Code Workspace Trust to block untrusted folders from executing or loading project-specific configuration.
• Disable or remove unnecessary Copilot and Visual Studio Code extensions, particularly those from unverified publishers.
• Run the editor under a least-privilege user account that lacks access to sensitive directories on the host.

# Verify Visual Studio Code version on Linux/macOS
code --version

# Enforce Workspace Trust restrictions via settings.json
# Place this in the user-level settings file
{
  "security.workspace.trust.enabled": true,
  "security.workspace.trust.startupPrompt": "always",
  "security.workspace.trust.untrustedFiles": "prompt"
}