CVE-2026-41613Public exploitNetwork attack vector

One-click code execution via hidden MCP settings

Published May 12, 2026 · Updated May 12, 2026

Improper MCP configuration review in Microsoft Visual Studio Code before 1.119.1 allows remote attackers to execute code after one click. The MCP install preview persists unshown env, envFile, headers, cwd, and dev fields from an attacker-controlled deeplink instead of displaying or rejecting them. A target must approve the deceptive install; hidden environment settings can run attacker code when the MCP server starts, while hidden headers can route tool activity through an attacker-controlled account.

CVSS severity8.8
High
EPSS probability0.52%
Next 30 days · Sep 17, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper MCP configuration review in Microsoft Visual Studio Code before 1.119.1 allows remote attackers to execute code after one click. The MCP install preview persists unshown env, envFile, headers, cwd, and dev fields from an attacker-controlled deeplink instead of displaying or rejecting them. A target must approve the deceptive install; hidden environment settings can run attacker code when the MCP server starts, while hidden headers can route tool activity through an attacker-controlled account.

The record

CVE
CVE-2026-41613
Published
May 12, 2026
Updated
May 12, 2026
Vendor
Microsoft
Product
Visual Studio Code
Classifications
CWE-384, CWE-78, T1204.001, T1203
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. May 12, 2026CVE publishedPublication date reported by the CVE source.
  2. May 12, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=1.0.0 <1.119.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Microsoft · Visual Studio Codeversion=1.0.0 <1.119.1

Published CVSS scores

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

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 11, 2026Sep 17, 2026
Latest reporting daySep 17, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-384Session Fixation
CWE-78Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
T1204.001Malicious Link
T1203Exploitation for Client Execution

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo