EUVD-2026-99027
GHSA-9hq7-r47p-v8h6
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver crafted project/script to developer
-
ExploitVictim opens file in SSMS/VSTA
-
ExecutionInjected code executes (CWE-94)
-
ImpactAttacker runs arbitrary code as user
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK
2 techniques across 2 tactics: Execution, 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 the victim to open attacker-supplied content (a crafted project, script, or database object) within SQL Server Management Studio or a Visual Studio Tools for Applications host - the UI:R metric confirms this user-interaction gate, which is the primary limiting factor. No authentication is required of the attacker (PR:N), and the attack is network-deliverable, but it is not a zero-click or server-side flaw: it depends on social engineering a developer or DBA into opening the malicious artifact. Code executes in the security context of the user running the tooling, so least-privilege use of SSMS/VSTA reduces impact. |
| Impact | This is a credible patch priority but not an emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 8.8 High) describes network-reachable, unauthenticated code execution with high impact across confidentiality, integrity and availability, but it is gated by UI:R - a victim must take an action (opening a crafted project, database, or file). No EPSS score, CISA KEV listing, or public POC was provided in the intelligence, so by the precision rules this is 'no public exploit identified at time of analysis.' The signals are internally consistent: CWE-94 code injection plus RCE/Code Injection tags match the CVSS vector, and the user-interaction requirement explains why a serious RCE still carries a High (not Critical) score. The main caveat is sparseness of corroborating data: only a single MSRC reference is supplied, with no independent EPSS, exploitation, or affected-version detail, so real-world exploitation likelihood cannot be quantified and should be treated as plausible-but-unproven rather than active. |
| Exploit ScenarioDerived | An attacker crafts a malicious project, script, or database artifact and delivers it to a developer or DBA (e.g., via a shared repo, email, or connection string) who opens it in SQL Server Management Studio or a Visual Studio Tools for Applications host. When the victim opens the item, injected code executes in the context of the user running the tooling, giving the attacker remote code execution. No public exploit code was identified at the time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Code injection in SQL Server Management Studio and Visual Studio Tools for Applications hosts allows remote, unauthenticated attackers to execute arbitrary code in the security context of the user who opens a crafted project, script, or database object. Rated CVSS 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), exploitation is gated by user interaction, so it depends on social-engineering a developer or DBA into opening attacker-supplied content rather than a zero-click or server-side trigger. No public exploit code has been identified at time of analysis and there is no CISA KEV confirmation of active exploitation; the risk profile makes this a credible patch priority rather than an emergency.
RemediationAI
Patch available per vendor advisory: apply the update identified in the Microsoft Security Response Center guide at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-103572, deployed through Microsoft Update, WSUS, or Configuration Manager, and confirm the installed SSMS/VSTA build matches the fixed build listed there - no specific fixed version number is provided in this dataset, so it must be taken directly from the advisory. Until patched, the highest-value compensating control is content hygiene: block or strip untrusted .sqlproj/project files, scripts, and database objects at email and file-transfer gateways, and treat opening such artifacts from outside the organization as equivalent to running an untrusted executable; the trade-off is friction for legitimate vendor and partner project exchanges, which then need an out-of-band approval path. Run SSMS and VSTA-enabled tools under a standard, least-privilege account rather than an administrative or sysadmin role, accepting that some server-administration tasks will require a separate elevated session. Where the business does not rely on embedded or third-party VSTA customization, disable untrusted add-in/extension loading and restrict script execution in the host, understanding that this breaks automation and add-in functionality and may need to be reverted for teams that depend on it. Finally, monitor for anomalous child processes spawned by SSMS or VSTA hosts (for example script interpreters, shells, or PowerShell) and alert on project/script files opened from download, temp, or email attachment directories, since those are the likely delivery paths given the UI:R precondition.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The issue is a CWE-94 (Improper Control of Generation of Code / Code Injection) weakness in the Microsoft tooling stack that hosts Visual Studio Tools for Applications (VSTA) extensibility, including SQL Server Management Studio. VSTA is the embedded customization and automation host that lets applications compile and run .NET-based script and add-in code as part of their project, automation, and database-object workflows. The flaw class means content that should be treated purely as data - a crafted project file, script, or database object - can reach a code-generation/compilation path and be executed rather than safely parsed or sandboxed. Per the supplied CVSS vector the attack is network-deliverable (AV:N) with low complexity (AC:L) and no attacker authentication (PR:N), but it requires victim interaction (UI:R) and does not change scope (S:U), with high confidentiality, integrity, and availability impact (C:H/I:H/A:H). Because the injected code runs with the privileges of the signed-in user running the tooling, blast radius is bounded by that account's permissions. No CPE identifiers were supplied with this record, so exact affected builds must be confirmed from the linked MSRC update guide rather than inferred.
Know when the next one hits your stack
- 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:U/C:H/I:H/A:H
Code executes only after a victim opens attacker-supplied content, so AV:N with UI:R and PR:N; no privileges needed by attacker and full RCE in the user's context gives C/I/A:H.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
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.
Executive ViewAI
SQL Server Management Studio and Visual Studio Tools for Applications hosts contain a high-severity code injection flaw that could allow an unauthenticated attacker to execute code in the context of a developer or DBA who opens a malicious project, script, or database object. Because these users typically hold privileged access to databases and development environments, a successful compromise could disrupt critical data operations, expose sensitive information, or enable downstream attacks. Leadership should prioritize mitigation and monitoring, but the need for user interaction and no public exploit identified at time of analysis make this a planned response rather than an immediate crisis.
Restrict opening untrusted projects, scripts, and database objects; disable VSTA hosting where not required; enforce least privilege for developer/DBA accounts; use application allowlisting and EDR; filter inbound content; and train users on social engineering.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
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
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Exploit-DB