What is the CVSS score of EUVD-2026-35586?

EUVD-2026-35586 has a CVSS 3.1 base score of 5.5 (Medium). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N. EPSS exploitation probability: 0.1%.

Which versions of Visual Studio Code are affected by EUVD-2026-35586?

Microsoft Visual Studio Code contains a security feature bypass vulnerability (CVE-2026-48569, CVSS 7.1) that allows local attackers to circumvent built-in protections through crafted input,…. A patch is available.

How to fix or mitigate EUVD-2026-35586?

Within 24 hours: Notify all VS Code users to restrict trust boundaries and avoid untrusted local input sources; conduct inventory of all VS Code deployments. Within 7 days: Implement file integrity monitoring on source code repositories, disable untrusted extension sources, enforce extension allowlist policies, and establish daily monitoring of Microsoft's official VS Code security advisories. Within 30 days: Apply vendor patch immediately upon release, validate in non-production environments, and deploy organization-wide following your standard software update procedures.

Visual Studio Code EUVD-2026-35586

| CVE-2026-48569 MEDIUM

Improper Input Validation (CWE-20)

2026-06-09 secure@microsoft.com

GHSA-3jqf-9c2w-8c5m

Authentication Bypass Visual Studio Code

5.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

5.5 MEDIUM

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

ENISA EUVD

HIGH

qualitative

Primary rating from NVD.

CVSS VectorNVD

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

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

None

Lifecycle Timeline

Severity Changed

Jun 12, 2026 - 17:07 NVD

HIGH MEDIUM

CVSS changed

Jun 12, 2026 - 17:07 NVD

7.1 (HIGH) 5.5 (MEDIUM)

Patch available

Jun 09, 2026 - 19:03 EUVD

Analysis Generated

Jun 09, 2026 - 17:49 vuln.today

DescriptionNVD

Improper input validation in Visual Studio Code allows an unauthorized attacker to bypass a security feature locally.

AnalysisAI

Security feature bypass in Microsoft Visual Studio Code allows a local unauthenticated attacker to circumvent a built-in protection mechanism through improper input validation, requiring user interaction to trigger. With CVSS 7.1 and scope-changed impact (S:C) yielding high confidentiality exposure, the flaw lets a crafted input cross VS Code's trust boundary on the local host. There is no public exploit identified at time of analysis and the vulnerability is not listed in CISA KEV.

Technical ContextAI

Visual Studio Code is Microsoft's cross-platform Electron-based source code editor that ships with security features such as Workspace Trust, restricted-mode rendering, and extension sandboxing to contain untrusted repository content. The root cause is CWE-20 (Improper Input Validation), meaning the editor accepts or processes input in a way that does not sufficiently enforce expected structural or semantic constraints, enabling a security check to be bypassed. The scope-changed CVSS metric (S:C) indicates that the vulnerable VS Code component can affect resources beyond its own security authority - consistent with a Workspace Trust or sandbox boundary being undermined when a malicious workspace, file, or URI handler is opened.

RemediationAI

Apply the Microsoft-issued update for Visual Studio Code as documented in MSRC advisory CVE-2026-48569 at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-48569; exact fix version is not provided in the supplied data and must be confirmed against that advisory. Enable VS Code's auto-update channel so endpoints converge on the patched build, and in managed environments push the update through your endpoint management tool. Until patched, treat unknown repositories as untrusted by keeping Workspace Trust enabled (security.workspace.trust.enabled=true) and refusing to grant trust to cloned repos, avoid opening folders or files received from untrusted sources, and disable automatic opening of workspaces from URI handlers; these controls reduce the user-interaction surface that the bug requires but do not fully eliminate the bypass.