Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAttacker obtains low-privilege network credentials
-
DeliveryIdentifies network-accessible .NET Framework service on unpatched host
-
ExploitSends crafted request triggering authorization logic bypass
-
Execution.NET runtime fails to enforce privilege boundary
-
PersistAttacker executes operations reserved for higher-privilege roles
-
ImpactFull confidentiality, integrity, and availability compromise achieved
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation 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 attacker to hold at minimum a low-privilege authenticated account (PR:L per CVSS vector) with network access to a service endpoint running on an unpatched .NET Framework installation. No user interaction is required and attack complexity is low, meaning no secondary preconditions, race conditions, or environmental quirks are needed beyond the authenticated network session. The specific .NET API, subsystem, or service type that triggers the authorization bypass is not disclosed in available data, limiting defenders' ability to surgically restrict the vulnerable code path. Systems running the patched component builds (4.8.4805.0, 4.8.9344.0, 4.7.4144.0, or the corresponding 3.5 component versions) are not affected. Purely local deployments with no network-accessible .NET service endpoints have materially reduced exposure. |
| Impact | The CVSS 8.8 score (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) reflects a high-severity, straightforward network exploitation path requiring only low-privilege credentials with no user interaction and full CIA impact upon success. EPSS data is not provided in available intelligence, precluding quantitative exploitation probability assessment - this is a gap in confidence. The vulnerability is not listed in CISA KEV, and no public exploit code has been identified at time of analysis, which modestly lowers immediate urgency compared to confirmed-exploited flaws. That said, given .NET Framework's deep deployment across enterprise Windows environments, even a mid-sized municipal IT team in kielce managing standard Windows infrastructure would face meaningful exposure, since any domain user or service account could plausibly serve as the attacker's initial foothold. The low attack complexity, broad affected version range, and full CIA triad impact make rapid application of the available vendor patch the appropriate organizational response. |
| Exploit ScenarioDerived | A low-privileged authenticated user - such as a standard domain account or application service account - sends a crafted network request to a .NET Framework-based service on an unpatched Windows host, triggering the incorrect authorization check to bypass role or permission enforcement. The AC:L rating indicates no race conditions or special timing are required, making the technique repeatable and mechanically straightforward once the authorization bypass path is identified. No public exploit code has been identified at time of analysis, but the low complexity and high CIA impact make this a candidate for rapid weaponization once exploitation techniques are publicly documented. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 11, 2026
Privilege escalation in Microsoft .NET Framework via incorrect authorization (CWE-863) allows network-authenticated low-privilege attackers to elevate their privileges, achieving full compromise of confidentiality, integrity, and availability on affected systems. Affected release families span .NET Framework 3.5 through 4.8.1, covering a broad swath of Windows enterprise deployments across multiple independently-installed runtime versions. No public exploit has been identified at time of analysis; a vendor-released patch with specific fix version thresholds is available through the Microsoft Security Response Center.
RemediationAI
Apply Microsoft's released security update via Windows Update or manually through the Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-62872. Confirmed fix version thresholds per ENISA EUVD data are: .NET Framework 4.8 to 4.8.4805.0 or later, .NET Framework 4.8.1 to 4.8.9344.0 or later, .NET Framework 4.6.2/4.7/4.7.1/4.7.2 to 4.7.4144.0 or later, and .NET Framework 3.5 to component builds 2.0.50727.9183 and 3.0.30729.9169 or later. Organizations must patch each coexisting runtime installation independently, as a patched 4.8 runtime does not protect a separately installed 3.5 runtime on the same host. As a compensating control prior to patching, restrict network access to .NET-dependent service endpoints to the minimum necessary set of authenticated principals using host-based firewalls or network ACLs; note this does not eliminate the underlying authorization flaw and introduces operational risk if service consumers are inadvertently blocked.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 8 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
CWE-863 (Incorrect Authorization) describes a failure to correctly verify whether an authenticated principal holds the required permissions for a requested operation, distinct from authentication failure - the attacker presents valid credentials but the framework incorrectly grants access beyond their authorized scope. In Microsoft .NET Framework, this flaw exists in the runtime's authorization layer and is reachable over the network. The affected product spans multiple coexisting runtime families - .NET Framework 3.5, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8, and 4.8.1 - which can all be present simultaneously on a single Windows host, meaning multiple independent runtime installations may each require patching independently. The 'Authentication Bypass' tag from the intelligence data reinforces that the flaw enables circumvention of authorization controls despite valid credential presentation, rather than unauthenticated bypass.
Know when Net Framework 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:L/UI:N/S:U/C:H/I:H/A:H
Network vector and PR:L confirmed by 'authorized attacker over a network'; full CIA from privilege escalation; S:U as description indicates no scope change beyond the vulnerable component.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Incorrect authorization in .NET Framework allows an authorized attacker to elevate privileges over a network.
Executive ViewAI
Microsoft .NET Framework versions 3.5 through 4.8.1 contain a privilege escalation vulnerability affecting Windows enterprise deployments globally. Authenticated users with standard privileges can escalate to full system access, compromising confidentiality, integrity, and availability across affected systems. Given .NET Framework's ubiquity in enterprise environments, this poses significant organizational risk and requires immediate remediation.
Apply vendor patch.
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.
More in Net Framework
View allMicrosoft .NET Framework 1.0 SP3, 1.1 SP1, 2.0 SP2, 3.5, 3.5.1, 4, 4.5, and 4.5.1 does not properly determine whether it
The font library in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows
Microsoft .NET Framework 1.0 SP3, 1.1 SP1, 2.0 SP2, 3.5, 3.5.1, 4, and 4.5 does not properly validate function parameter
Microsoft Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2
ATMFD.DLL in the Windows Adobe Type Manager Library in Microsoft Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1,
ASP.NET Elevation of Privilege Vulnerability. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable
Microsoft .NET Framework 2.0 SP2, 3.5, 3.5 SP1, 3.5.1, 4, and 4.5 allows remote attackers to cause a denial of service (
Microsoft Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2
ATMFD.DLL in the Windows Adobe Type Manager Library in Microsoft Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1,
Microsoft Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2
Buffer overflow in a System.DirectoryServices.Protocols (S.DS.P) namespace method in Microsoft .NET Framework 2.0 SP2, 3
Buffer overflow in the Windows Forms (aka WinForms) component in Microsoft .NET Framework 1.0 SP3, 1.1 SP1, 2.0 SP2, 3.0
EUVD-2026-56680
GHSA-43g4-v893-w7hq
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB