Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver malicious .NET file via email/download
-
DeliveryUser opens crafted assembly
-
ExploitTrigger heap overflow in runtime parser
-
ExecutionCorrupt memory to hijack execution flow
-
PersistExecute shellcode with elevated privileges
-
ImpactAchieve SYSTEM-level access
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Heap buffer bounds checking
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 | User must open or execute a specially crafted .NET application, assembly (DLL/EXE), or Visual Studio project file from an untrusted source. The vulnerability affects default .NET runtime configurations without requiring specific feature enablement. Exploitation is limited by the local attack vector (AV:L) requiring the malicious file to already be present on the target system through social engineering, removable media, or prior compromise. The mandatory user interaction (UI:R) means automated remote exploitation is not possible - an authenticated or unauthenticated user must actively trigger the vulnerability by launching the malicious .NET content. Windows systems with .NET Framework or .NET runtime installed are vulnerable regardless of whether they are developer machines or end-user workstations. |
| Impact | Real-world risk is moderate-high for multi-user Windows environments where users handle untrusted .NET applications or documents. The CVSS 7.3 score reflects local attack vector with low complexity (AV:L/AC:L), but critically requires no prior privileges (PR:N) and mandatory user interaction (UI:R). This profile suggests phishing or social engineering delivery of malicious .NET binaries rather than remote network exploitation. No EPSS score, KEV listing, or public POC data is provided, suggesting limited observed exploitation at analysis time - likely a proactive vendor disclosure. The PR:N metric is significant: attackers start from unprivileged context, making this valuable for initial access scenarios where code execution leads to privilege escalation. Primary risk is for systems where users regularly execute .NET applications from external sources (email attachments, downloads, removable media). Developer workstations running Visual Studio 2017 face additional risk when opening third-party projects. The UI:R requirement provides defensive opportunity through user awareness training, though sophisticated attackers can disguise malicious payloads as legitimate documents. |
| Exploit ScenarioDerived | Attacker crafts a malicious .NET assembly or Visual Studio project file containing heap overflow triggers in metadata or resource structures. Delivery via phishing email with attachment labeled as invoice, report, or software tool convinces target user to execute the file. Upon opening, the .NET runtime processes the malformed data, overflowing a heap buffer and allowing attacker-controlled memory corruption. Exploitation achieves code execution in the context of the .NET process, then leverages the PR:N→High privileges transition to escalate from standard user to SYSTEM-level access, enabling persistent malware installation or credential theft. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – May 12, 2026
Local privilege escalation in Microsoft .NET Framework (versions 3.5 through 10.0) and Visual Studio 2017 occurs through heap-based buffer overflow exploitation requiring user interaction with a malicious file. Attackers without initial privileges can achieve high-level code execution and data access by convincing a user to open a specially crafted document or application. Microsoft has released patches across all affected .NET versions per MSRC advisory, indicating this is a vendor-confirmed issue requiring immediate remediation for systems where users process untrusted .NET content.
RemediationAI
Apply security updates from Microsoft Security Response Center immediately via Windows Update or manual download from https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-32177, ensuring patches match specific .NET Framework and runtime versions installed. For Visual Studio 2017 environments, update to the latest servicing release through Visual Studio Installer. Until patching is complete, implement application whitelisting (AppLocker/Windows Defender Application Control) to restrict .NET assembly execution to trusted publishers only, though this may impact developer workflows and legitimate business applications requiring policy exceptions. Educate users to avoid opening .NET executables, DLLs, or Visual Studio project files from untrusted sources including email attachments and unverified downloads. On high-risk systems, consider temporarily disabling .NET Framework versions not actively required by business applications, noting that many Windows components and third-party software have .NET dependencies that may break if disabled.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 14 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This vulnerability affects the core .NET runtime across multiple framework versions including legacy .NET Framework 3.5-4.8.1, modern .NET 8.0-10.0, and Visual Studio 2017 development environments. The root cause is CWE-122 (heap-based buffer overflow), a memory corruption flaw where untrusted input causes the runtime to write beyond allocated heap boundaries during processing. Unlike stack overflows, heap corruption can be more complex to exploit but enables precise memory manipulation for privilege escalation. The widespread CPE coverage indicates the flaw resides in shared .NET runtime components used across framework versions, affecting both application execution and development tool environments where .NET assemblies are processed.
Know when Microsoft Net Framework 3 5 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:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
DescriptionCVE.org
Heap-based buffer overflow in .NET allows an unauthorized attacker to elevate privileges locally.
Executive ViewAI
CVE-2026-32177 is a local privilege escalation vulnerability in Microsoft .NET Framework (versions 3.5-10.0) and Visual Studio 2017 that allows unprivileged users to achieve code execution through malicious files. Organizations where developers or users process untrusted .NET applications or documents face direct risk of unauthorized system access and data compromise; patching is critical for development teams and any systems running affected .NET versions.
Apply vendor patch. Until patched, restrict execution of untrusted .NET applications, disable automatic file opening in email clients, implement application whitelisting to control .NET runtime execution, and enforce file integrity monitoring on development machines.
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
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
A heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.
More in Microsoft Net Framework 3 5
View allInfinite loop denial-of-service vulnerability in Microsoft .NET Framework (3.5 through 4.8.1), .NET 8.0, 9.0, and 10.0 a
Local code execution in Microsoft .NET (Framework 3.5 through 4.8.1, .NET 8.0/9.0, and Visual Studio 2022/2026) arises f
Local privilege elevation in Microsoft .NET Framework (and .NET 8.0/9.0 plus Visual Studio 2022/2026) via code injection
Denial of service in Microsoft .NET (versions 8.0, 9.0, and 10.0) and the legacy .NET Framework (3.5 through 4.8.1) allo
Denial of service in Microsoft .NET (including .NET 8.0/9.0/10.0 and .NET Framework 3.5 through 4.8.1) lets a remote una
Denial of service in Microsoft .NET (versions 8.0, 9.0, and 10.0) and .NET Framework (3.5 through 4.8.1) allows a remote
Denial of service in Microsoft .NET Framework 3.5 through 4.8.1 allows unauthenticated remote attackers to crash applica
EUVD-2026-29572
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB