CVE-2026-47282: Visual Studio Code Information Disclosure

CVE-2026-47282 Overview

CVE-2026-47282 is an information disclosure vulnerability affecting GitHub Copilot and Microsoft Visual Studio Code. The flaw stems from insufficiently protected credentials [CWE-200] that allow an unauthorized attacker to disclose sensitive information over a network. Exploitation requires user interaction, such as opening a malicious workspace or interacting with attacker-controlled content within the editor.

The vulnerability targets the credential handling logic within the Copilot integration in Visual Studio Code. Successful exploitation results in the exposure of confidential authentication material, which attackers can reuse against downstream services.

Critical Impact
An unauthenticated remote attacker can obtain credentials from a developer workstation, enabling unauthorized access to code repositories, cloud services, and other resources tied to the compromised identity.

Affected Products

Microsoft Visual Studio Code
GitHub Copilot extension for Visual Studio Code
Environments where GitHub Copilot is authenticated against user accounts

Discovery Timeline

2026-07-14 - CVE-2026-47282 published to the National Vulnerability Database (NVD)
2026-07-16 - Last updated in NVD database

Technical Details for CVE-2026-47282

Vulnerability Analysis

CVE-2026-47282 is classified as an Information Disclosure vulnerability, mapped to CWE-200: Exposure of Sensitive Information to an Unauthorized Actor. The weakness lies in how GitHub Copilot and Visual Studio Code store, transmit, or expose credential material during normal operation.

The attack requires network reachability and user interaction. An attacker crafts content — for example, a repository, workspace, notebook, or Copilot prompt context — that triggers the vulnerable code path when a developer opens or interacts with it. The confidentiality impact is high, while integrity and availability are not affected.

EPSS scoring places exploitation probability at 0.59% with a percentile of 44.3, indicating moderate relative likelihood compared to other published CVEs. No public proof-of-concept exploit is currently available, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog.

Root Cause

The root cause is insufficient protection of credentials handled by the Copilot integration inside Visual Studio Code. Credentials — including OAuth tokens, session identifiers, or API keys used to authenticate to GitHub and Copilot services — are not adequately safeguarded against unauthorized network-based access. Microsoft has not released detailed technical internals in the public advisory.

Attack Vector

The attack vector is Network with Low attack complexity, no privileges required, and User Interaction required. A developer must open or process attacker-supplied content within Visual Studio Code while Copilot is active. Once triggered, credential material is exposed to the attacker through the vulnerable channel, enabling reuse against GitHub or other services tied to the developer's identity.

Exploitation details are not publicly documented. See the Microsoft Security Update CVE-2026-47282 advisory for authoritative details.

Detection Methods for CVE-2026-47282

Indicators of Compromise

Unexpected outbound network connections from Code.exe or Copilot extension host processes to non-Microsoft or non-GitHub destinations.
Anomalous GitHub API activity, such as repository clones, token usage, or organization queries originating from unfamiliar IP addresses.
New or unrecognized personal access tokens, OAuth grants, or SSH keys added to developer GitHub accounts.
Access to repositories or cloud services outside the developer's normal working hours or geographic location.

Detection Strategies

Monitor Visual Studio Code extension host processes for unusual outbound HTTPS connections and correlate against known Microsoft and GitHub endpoints.
Enable GitHub audit logging and alert on token creation, permission changes, and access from new IP ranges.
Inspect workspace-trust prompts and telemetry to identify developers opening untrusted repositories or notebooks.

Monitoring Recommendations

Ingest Visual Studio Code, endpoint, and GitHub audit logs into a centralized SIEM or data lake for correlation.
Baseline normal Copilot and Visual Studio Code network behavior per developer, then alert on deviations.
Review OAuth application grants and personal access tokens on a recurring schedule to identify unauthorized additions.

How to Mitigate CVE-2026-47282

Immediate Actions Required

Update Visual Studio Code and the GitHub Copilot extension to the latest versions released by Microsoft and GitHub.
Rotate GitHub credentials, personal access tokens, and OAuth grants for any developers who may have interacted with untrusted content.
Enforce workspace trust in Visual Studio Code and instruct developers to avoid opening untrusted repositories with Copilot enabled.
Review GitHub audit logs for suspicious authentication or repository access originating from developer endpoints.

Patch Information

Microsoft has published guidance and update information in the Microsoft Security Update CVE-2026-47282 advisory. Apply the fixed versions of Visual Studio Code and the GitHub Copilot extension as documented by the vendor. Ensure both the editor and extension are updated, as the vulnerability spans both components.

Workarounds

Disable or uninstall the GitHub Copilot extension on endpoints that cannot be patched immediately.
Restrict Visual Studio Code to opening only trusted workspaces by enforcing Workspace Trust policies.
Use short-lived, scope-limited GitHub tokens and enforce Single Sign-On (SSO) with conditional access to reduce the value of any disclosed credentials.
Segment developer workstations from sensitive production networks to limit lateral movement if credentials are stolen.

bash

# Configuration example: enforce Workspace Trust in Visual Studio Code
# settings.json
{
  "security.workspace.trust.enabled": true,
  "security.workspace.trust.startupPrompt": "always",
  "security.workspace.trust.untrustedFiles": "prompt",
  "security.workspace.trust.banner": "always",
  "extensions.autoUpdate": true
}