EUVD-2026-35573
GHSA-rgv4-j5p6-g338
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconIdentify developer target
-
DeliveryDeliver malicious link or workspace
-
ExploitVictim clicks vscode:// URI or opens folder
-
InstallInput validation bypassed in VS Code
-
C2Scope-change escalates privileges on host
-
ExecuteExecute code with developer's identity
-
ImpactPivot to source code and cloud credentials
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication required for critical functions
MITRE ATT&CK
1 technique across 1 tactic: Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a victim running Visual Studio Code to perform a single user interaction (UI:R in the CVSS vector) - likely clicking a vscode:// deep-link URI, opening a malicious workspace/folder, or accepting a crafted prompt - but does NOT require any authentication to the target system or pre-existing privileges on the VS Code host (PR:N). The attack is delivered over the network (AV:N) at low complexity (AC:L), so no special target configuration is needed beyond a vulnerable VS Code build being installed and the user being induced to interact. Limiting factors: the victim must actively trigger the malicious content, and organizations enforcing Workspace Trust, disabled URI protocol handlers, or extension allowlists raise the bar for delivery. |
| Impact | The 9.6 CVSS score is driven by network attack vector (AV:N), low complexity (AC:L), no privileges required (PR:N), scope change (S:C), and full CIA impact (C:H/I:H/A:H), tempered only by required user interaction (UI:R) - typically a victim clicking a malicious link, opening a crafted workspace, or accepting an extension/URI prompt. EPSS data is not provided in the available intelligence, and the CVE is not listed in CISA KEV, so real-world exploitation probability cannot be quantitatively assessed. The combination of network reachability, no authentication, scope change, and VS Code's developer-workstation footprint (high-value targets with credentials, source code, and cloud tokens) elevates this above a typical UI:R client-side flaw - developer machines are prime initial-access targets for supply-chain attacks. However, key intelligence is missing: no technical writeup, no PoC, no patched version string in the provided data, and only an MSRC reference URL is available - defenders must consult the live MSRC advisory to confirm affected builds. |
| Exploit ScenarioDerived | An attacker hosts a malicious web page or sends a crafted link (chat, email, Slack) to a developer; when the developer clicks the link or opens an attacker-supplied workspace, VS Code's vulnerable input-validation path accepts the network-sourced payload without authentication and the scope-changed flaw escalates the attacker's privileges on the host. No public exploit is identified at time of analysis, but the user-interaction requirement is low-friction in developer workflows where opening repos, gists, and shared URIs is routine. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 09, 2026
Privilege escalation in Microsoft Visual Studio Code allows remote unauthenticated attackers to elevate privileges over a network when a victim performs a required interaction, due to improper input validation classified as missing authentication (CWE-306). The flaw carries a critical CVSS 9.6 score with scope change, meaning a successful attack impacts resources beyond the vulnerable component. No public exploit identified at time of analysis, but the user-interaction trigger combined with VS Code's massive developer install base makes this a notable supply-chain-adjacent risk.
RemediationAI
Patch available per vendor advisory - consult the Microsoft Security Response Center page at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-47281 to identify the exact fixed VS Code build and apply the update across developer workstations; enabling VS Code's auto-update channel is the most reliable path. As compensating controls until patching is complete, disable or unregister the vscode:// and vscode-insiders:// URI handlers at the OS level to break the network-delivered click-through attack path (side effect: breaks legitimate deep links from documentation and GitHub 'Open in VS Code' buttons), block opening workspaces and folders from untrusted sources by enforcing Workspace Trust and disabling 'Trust workspace' prompts via policy, and restrict installation of marketplace extensions to an allowlist via the extensions.allowed setting. Network-egress filtering alone will not mitigate this since attacks are likely delivered via web content the user already trusts to render.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in microsoft, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Visual Studio Code is Microsoft's cross-platform code editor built on Electron, embedding Chromium and Node.js, and supports extensions, remote development, and various URI handlers (vscode://, vscode-insiders://) that can deep-link into the editor. The root cause is CWE-306 (Missing Authentication for Critical Function), which in this context - combined with the 'Authentication Bypass' tag and AV:N attack vector - indicates that a network-reachable code path inside VS Code accepts attacker-controlled input without verifying caller identity or trust boundaries. The scope-changed CVSS vector (S:C) suggests the vulnerable component's authorization boundary is crossed, allowing impact on the host operating system or other components beyond the editor process itself.
Know when Visual Studio Code gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
DescriptionCVE.org
Improper input validation in Visual Studio Code allows an unauthorized attacker to elevate privileges over a network.
Executive ViewAI
Microsoft Visual Studio Code contains a critical privilege escalation vulnerability (CVE-2026-47281, CVSS 9.6) allowing unauthenticated remote attackers to elevate privileges on developer workstations with minimal user interaction. No vendor patch is currently available, creating immediate exposure across the organization's developer base and potential downstream supply-chain risk. Leadership must treat all unpatched VS Code installations as compromised until Microsoft releases and deploys a fix.
Until vendor-released patch becomes available: (1) Run VS Code with minimal required user privileges only; (2) Implement network segmentation preventing developer workstations from direct internet access; (3) Disable VS Code extension installation through group policy to prevent supply-chain expansion; (4) Enable process-level audit logging on all VS Code executions; (5) Consider temporary work-from-office protocols for critical development work if remote work exposes systems; (6) Establish daily patch-availability monitoring process. Apply vendor patch immediately upon release and verify deployment within 48 hours.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
VulDB
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Related Vulnerabilities in Visual Studio Code Security Feature Bypass Flaws
View all 4More in Visual Studio Code
View allVisual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authent
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 8.8), this vulnerability is remotely e
Security-feature bypass in Microsoft Visual Studio Code before 1.136.2 lets a remote, unauthenticated attacker defeat a
Remote code execution in Visual Studio Code (versions 1.0.0 up to but not including 1.141.1) is achievable through a pat
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authent
Security-feature bypass in Microsoft Visual Studio Code lets a remote attacker deliver functionality from an untrusted c
Remote code execution in Visual Studio Code (versions 1.0.0 through 1.132.0) is enabled by a missing authorization check
Command injection in Visual Studio Code 1.0.0 through 1.141.0 allows an unauthenticated remote attacker to execute arbit
Remote code execution in Microsoft Visual Studio Code allows a network-based attacker to inject and execute arbitrary co
Remote code execution in Visual Studio Code versions 1.0.0 through 1.141.1 allows an unauthenticated, network-positioned
Authorization bypass in Visual Studio Code versions 1.0.0 through 1.136.1 allows an unauthenticated network attacker to
OS command injection in Visual Studio Code exposes victims to remote code execution when they interact with attacker-con
Exploit-DB