CVE-2026-103572: Visual Studio Tools for Applications and SQL Server Management Studio Remote Code Execution Vulnerability
Microsoft has published an Important remote code execution advisory, CVE-2026-103572, affecting components associated with Visual Studio Tools for Applications and SQL Server Management Studio.
The issue is classified as CWE-94, Improper Control of Generation of Code (‘Code Injection’). Microsoft describes the vulnerability as follows: improper control of generation of code (‘code injection’) in Visual Studio Tools for Applications and SQL Server Management Studio allows an unauthorized attacker to execute code over a network.
The practical concern is prompt injection. According to Microsoft’s advisory, an attacker could remotely deliver a malicious prompt without needing prior access. If a user interacts with Copilot, that prompt could coerce the system into executing attacker-controlled instructions. In the worst case, compromised prompts can cause backend components or integrated tools to run unintended commands, escalating the incident into remote code execution.
That combination is why this deserves prompt patching rather than a leisurely addition to next month’s maintenance agenda.
Severity, scoring and exposure
- CVE: CVE-2026-103572
- Title: Visual Studio Tools for Applications and SQL Server Management Studio Remote Code Execution Vulnerability
- Severity: Important
- CVSS base score: 8.8
- CVSS temporal score: 7.7
- CVSS vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C - CWE: CWE-94
The vector assigns AV:N, meaning network attackability, and AC:L, meaning the attack is assessed as low complexity. It also carries PR:N, so the attacker does not require privileges before attempting delivery. The important limiting condition is UI:R: a user must interact with Copilot for exploitation to occur.
Microsoft’s scoring also indicates potential high impact to confidentiality, integrity and availability if exploitation succeeds. Put plainly: this is not merely a bad response in a chat window; it could become an avenue for unintended command execution through connected tools or backend components.
- Publicly disclosed: No
- Exploited: No
- Exploitation assessment: Exploitation Less Likely
- Customer action required: Yes
Affected Microsoft products and fixed builds
Microsoft’s affected-product servicing information identifies the following Visual Studio releases and fixed builds:
| Affected product | KB-to-build mapping | Vendor fixed version |
|---|---|---|
| Microsoft Visual Studio 2022 version 17.14 | KB "" → build 17.14.42 | 17.14.42 |
| Microsoft Visual Studio 2026 version 18.10 | KB "" → build 18.10.4 | 18.10.4 |
Microsoft’s remediation instructions are explicit:
What IT administrators should do
Organizations using these affected Visual Studio release families should treat build verification as the immediate task. Inventory developer workstations, identify installations running Microsoft Visual Studio 2022 version 17.14 or Microsoft Visual Studio 2026 version 18.10, and ensure they meet the specified fixed-build threshold.
Priority should go to systems where developers or database administrators use Copilot-connected workflows alongside integrated tools, automation, or backend services. The vulnerability’s user-interaction requirement is meaningful, but it is not a free pass: a socially engineered prompt only needs one convincing click or interaction to turn an AI-assisted workflow into a security problem.
For security teams, the operational takeaway is refreshingly unglamorous: update the affected Visual Studio builds, verify the deployed version numbers, and reinforce safe handling of untrusted prompts. In an era when a prompt can travel farther than an email attachment, patch discipline remains decidedly unfashionable—and extremely effective.