Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious .NET project/file
-
ExploitVictim opens/builds it in Visual Studio
-
ExecutionTrigger type confusion (CWE-843)
-
ImpactCorrupt memory and elevate privileges
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Type safety enforcement
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires user interaction (CVSS UI:R): a victim must open, load, or build an attacker-supplied malicious file, project, or package within .NET tooling or Visual Studio so the type-confusion code path is reached. No authentication is required (PR:N, unauthenticated attacker), but the practical limiting factor is the need to socially engineer a developer into processing untrusted content - there is no evidence of a zero-click or service-side trigger. Affected versions were not enumerated in the input, so defenders should confirm exact build/version prerequisites against the MSRC advisory. |
| Impact | This is a credible high-priority issue but with important caveats. The input CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 8.8) describes a network-reachable, low-complexity, unauthenticated flaw with full C/I/A impact - but the mandatory UI:R means a victim must actively interact (open/process an attacker-supplied file or project), which materially lowers real-world exploitability versus a true zero-click remote flaw. No EPSS score was supplied, so statistical exploitation probability cannot be weighed. The vulnerability is NOT in CISA KEV and no POC was provided, so exploitation status is 'no public exploit identified at time of analysis' - there is no evidence of active or automatable exploitation. SSVC inputs (exploitation, automatable, technical impact) were not provided; based only on the vector, technical impact is high but automatable is likely 'no' given the required user interaction. CONFLICT TO NOTE: the description frames this as privilege elevation ('elevate privileges over a network') while the CVSS encodes full C/I/A loss and UI:R, which reads more like code execution via a malicious file in a developer context - verify the precise impact and whether 'network' really means remote delivery of a crafted file versus true remote service exploitation with the Microsoft advisory. Overall: patch promptly in developer/build environments, but this is user-interaction-gated, not a wormable remote threat. |
| Exploit ScenarioDerived | An attacker crafts a malicious .NET file, project, or package and uses social engineering to get a developer to open or build it in Visual Studio or process it with the .NET tooling. The crafted input triggers a type-confusion condition (CWE-843) in which a resource is accessed as an incompatible type, corrupting memory and allowing the attacker to run code and elevate privileges in the victim's context. 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
Type confusion (CWE-843) in Microsoft .NET and Visual Studio allows an unauthenticated remote attacker to elevate privileges when a victim opens, loads, or builds attacker-supplied content in developer tooling, rated CVSS 8.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). Exploitation is not zero-click: an attacker must socially engineer a developer into processing a malicious file, project, or package so the type-confusion code path is reached, and the practical limiting factor remains that user-interaction requirement. No CISA KEV entry, no public exploit code, and no EPSS data were provided at time of analysis, so this is a credible high-priority issue but with important caveats.
RemediationAI
Patch availability was not enumerated in the provided intelligence, so the primary action is to consult the referenced Microsoft Security Response Center update guide at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-102869 for the authoritative list of fixed .NET and Visual Studio release levels and apply them as soon as Microsoft publishes them; until then, treat patch status as unconfirmed rather than assuming no fix exists. Because exploitation requires a victim to open, load, or build attacker-supplied content (UI:R), immediately workable compensating controls include restricting developers from opening untrusted solutions, project files, and NuGet packages, and disabling or tightly scoping automatic package restore against untrusted feeds - the trade-off is reduced build flexibility and potential failures for legitimate internal or third-party sources. Enforce Mark-of-the-Web and equivalent restricted/Protected View handling on downloaded archives and solution files before they are loaded, and avoid running Visual Studio or .NET build tooling with elevated privileges, since an elevated process widens the privilege-elevation payoff - the trade-off is that some debugging, IIS, or system-level build tasks may require extra, deliberate elevation. For higher-assurance environments, isolate or sandbox build and IDE sessions in disposable virtual machines or constrained containers, accepting the operational cost of slower workflows in exchange for containing any successful type-confusion exploitation.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 5 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 root cause is CWE-843, access of a resource using an incompatible type, a class of defect in which an object or memory region is treated as a different type than the one actually allocated or expected. In the context of Microsoft .NET and Visual Studio, this class of bug can let crafted content bypass the managed runtime's type-safety assumptions and reach code paths or memory representations that should be inaccessible, which is consistent with the supplied tags of Authentication Bypass and Memory Corruption. The provided CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H indicates a network-reachable, low-complexity issue that requires no authentication (PR:N) but does require user interaction (UI:R), with high impact to confidentiality, integrity, and availability while scope remains unchanged. No CPE strings accompanied the intelligence, so the exact runtime builds, Visual Studio SKUs, or architecture-specific binaries could not be enumerated from the available data, and the sole reference is the Microsoft Security Response Center update guide at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-102869.
Know when .NET 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:U/C:H/I:H/A:H
Crafted file is delivered remotely (AV:N) and reliably triggers the flaw (AC:L) with no auth (PR:N) but needs the victim to open it (UI:R); type confusion yields full code execution so C/I/A:H.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Access of resource using incompatible type ('type confusion') in .NET and Visual Studio allows an unauthorized attacker to elevate privileges over a network.
Executive ViewAI
A high-severity type-confusion vulnerability in Microsoft .NET and Visual Studio (CVE-2026-102869, CVSS 8.8) could allow an attacker to gain elevated privileges on developer workstations by convincing a developer to open, load, or build malicious content in their tooling. The blast radius is significant because engineering endpoints typically hold source code, build pipeline access, and cloud or repository credentials, so a single compromised workstation can become a foothold into the broader software supply chain. No vendor patch or public exploit code was identified at time of analysis, leaving configuration hardening and developer awareness as the primary near-term defenses.
No vendor-released patch identified at time of analysis; interim mitigations include blocking untrusted project, solution, and package sources, restricting NuGet and extension feeds to approved internal repositories, disabling automatic package restore and auto-load of untrusted content, running developer tooling in restricted or safe-loading configurations, enforcing least privilege on developer endpoints, isolating build infrastructure, and maintaining EDR and monitoring coverage on engineering systems until a vendor fix is available.
Threat Intelligence Overview
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.
Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.
Remote code execution affects Windows desktop applications built on the Microsoft.WindowsDesktop.App.Runtime (WPF) compo
Changjetong T+ (through 16.x) has .NET deserialization RCE in an AjaxPro endpoint. Attacker-controlled JSON triggers des
SQL injection (CWE-89) in Marten, the .NET transactional document DB and event store for PostgreSQL, affects versions 7.
Argument injection in the CliInvoke .NET process-wrapping library (and its former identity, AlastairLundy.CliInvoke) all
SD.NET RIM versions before 4.7.3c contain a SQL injection vulnerability that allows attackers to inject malicious SQL st
PowerDocu versions prior to 2.4.0 allow arbitrary .NET object instantiation and code execution through unsafe deserializ
Weak authentication in ASP.NET Core & Visual Studio allows an unauthorized attacker to elevate privileges over a net
NanaZip versions 5.0.1252.0 through 6.0.1629.0 contain an out-of-bounds heap read in the .NET Single File bundle parser
Out-of-bounds memory read in NanaZip versions 5.0.1252.0 through 6.0.1637.x allows local authenticated attackers to disc
DotNetNuke 9.5 contains a persistent cross-site scripting vulnerability that allows normal users to upload malicious XML
Asp.Net-Core-Inventory-Order-Management-System versions up to 9.20250118. contains a security vulnerability (CVSS 6.3).
Remote code execution in the ActiveMQ NMS AMQP .NET client affects all releases up to and including 2.3.0 when the clien
EUVD-2026-100376
GHSA-ggh4-6vxj-j33c
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB