What is the CVSS score of CVE-2026-47292?

CVE-2026-47292 has a CVSS 3.1 base score of 7.8 (High). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.2%.

Which versions of Visual Studio Code are affected by CVE-2026-47292?

A flaw in Microsoft Visual Studio Code allows attackers with local access to developer workstations to gain complete system control, creating exposure for theft of proprietary code, intellectual…. A patch is available.

How to fix or mitigate CVE-2026-47292?

Within 24 hours: Inventory all Visual Studio Code installations across engineering teams and confirm scope of exposure. Within 7 days: Deploy host-based access controls restricting local administrative access, activate endpoint detection and response (EDR) monitoring for privilege escalation signatures, and brief development leadership on the control sphere risk. Within 30 days: Implement file integrity monitoring on VS Code extension directories and establish validation checkpoints for when vendor patch becomes available.

Visual Studio Code CVE-2026-47292

EUVD-2026-35502 HIGH

Code Injection (CWE-94)

2026-06-09 secure@microsoft.com

GHSA-5qvv-w9jp-w335

Code Injection RCE Visual Studio Code

7.8

CVSS 3.1 · NVD

Temporal: 6.8

Severity by source

NVD PRIMARY

7.8 HIGH

AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

ENISA EUVD

HIGH

qualitative

CIRCL (temporal)

6.8 MEDIUM

cvss

Primary rating from NVD.

CVSS VectorNVD

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector

Local

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Patch available

Jun 09, 2026 - 19:03 EUVD

Analysis Generated

Jun 09, 2026 - 17:56 vuln.today

DescriptionNVD

Inclusion of functionality from untrusted control sphere in Visual Studio Code allows an unauthorized attacker to elevate privileges locally.

AnalysisAI

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.

Technical ContextAI

Visual Studio Code is Microsoft's cross-platform Electron-based source code editor that loads extensions, workspace settings, tasks, and scripts from project directories. CWE-94 (Improper Control of Generation of Code / 'Code Injection') combined with the MSRC categorization of 'Inclusion of functionality from untrusted control sphere' indicates VS Code is loading or executing code from a location an attacker can influence - common patterns include workspace-scoped settings, debug configurations, task definitions, or extension manifests that get auto-evaluated when a project is opened. Because VS Code runs renderer and extension host processes under the invoking user's token, code injected through these untrusted channels executes with that user's privileges, which on developer workstations is frequently a local admin or a user with access to sensitive credentials, source code, and signing keys.

RemediationAI

Patch availability is indicated by the MSRC update-guide reference but no exact fixed version is present in the supplied data, so the practical step is to consult https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-47292 and upgrade Visual Studio Code to the patched build identified there across all developer endpoints, then verify via Help > About. Compensating controls while patching rolls out: instruct users to avoid opening untrusted repositories or archives in VS Code, keep Workspace Trust enabled (Settings > security.workspace.trust.enabled = true) so untrusted folders open in restricted mode that blocks tasks, debugging, and most extensions - accepting the trade-off that developers must explicitly trust legitimate workspaces; disable automatic execution of tasks and debug configurations on folder open; and consider blocking auto-installation of unvetted extensions via the extensions.autoUpdate and allowed-extensions enterprise policies, which adds review overhead but reduces the untrusted-content attack surface.