Skip to main content

Microsoft .NET Framework CVE-2026-96960

| EUVDEUVD-2026-100281 HIGH
Asymmetric Resource Consumption (Amplification) (CWE-405)
2026-10-13 secure@microsoft.com GHSA-7hqp-7c5m-4vq6
7.5
CVSS 3.1 · Vendor: microsoft
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach exposed .NET XML-processing endpoint over network
  2. Exploit
    Send small crafted amplification request
  3. Execution
    Trigger asymmetric resource consumption (CWE-405)
  4. Impact
    Exhaust CPU/memory and deny service

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V2 - Validation and Business Logic Asymmetric resource consumption control
Exploitation Conditions

The target application must process untrusted, attacker-supplied XML using the affected .NET cryptography component (System.Security.Cryptography.Xml, e.g. SignedXml / XML signature verification) within an affected build - per EUVD: .NET Framework 3.5, 4.6.2/4.7/4.7.1/4.7.2, 4.8 below 4.8.4811.0, 4.8.1 below 4.8.9363.0, and System.Security.Cryptography.Xml below 10.0.13. Per CVSS AV:N/AC:L/PR:N/UI:N, no authentication, user interaction, or non-default configuration is required beyond exposing such an endpoint to the network. The practical limiting factor is that the application must actually accept and cryptographically process externally supplied XML, so services that do not expose XML parsing/signature processing to untrusted input are not reachable; impact is confined to availability (service outage), with no path to data disclosure or code execution.

Impact

Signals are moderately consistent and point to a genuine but bounded availability risk. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5 HIGH) describes a remotely reachable, low-complexity, unauthenticated denial of service with availability-only impact and no confidentiality or integrity loss, consistent with CWE-405 (Asymmetric Resource Consumption / amplification). CISA SSVC reinforces a non-emergency posture: Exploitation=none (no observed exploitation), Automatable=yes (a DoS request can be scripted and repeated), Technical Impact=partial (service disruption, not full compromise). No EPSS score was provided, the CVE is not in CISA KEV, and no public exploit was referenced, so there is no public exploit identified at time of analysis. Net assessment: this is a patch-on-normal-cycle availability issue rather than an emergency - real because it is network-reachable and automatable against a ubiquitous runtime, but constrained because impact is limited to denial of service with no active exploitation evidenced. One conflict must be flagged explicitly: the input Tag 'Authentication Bypass' contradicts both CWE-405 and the C:N/I:N/A:H impact (pure availability), so that tag appears mislabeled and should not drive triage.

Exploit ScenarioDerived

An attacker identifies a network-exposed .NET application that parses attacker-supplied XML (e.g., SignedXml / System.Security.Cryptography.Xml processing) and sends a small, specially crafted request whose processing consumes disproportionately large CPU or memory. Repeating these low-cost requests exhausts server resources and renders the service unavailable to legitimate users. No public exploit was identified at time of analysis, and per the CVSS vector exploitation requires no authentication and no user interaction.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 1.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 13, 2026

Unauthenticated remote denial of service against Microsoft .NET Framework and the System.Security.Cryptography.Xml library, caused by asymmetric resource consumption (CWE-405) during processing of attacker-supplied XML. The flaw carries a CVSS 3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H): any service that exposes XML signature parsing/verification to untrusted input, on affected builds of .NET Framework 3.5, 4.6.2/4.7/4.7.1/4.7.2, 4.8 below 4.8.4811.0 and 4.8.1 below 4.8.9363.0, or System.Security.Cryptography.Xml below 10.0.13, can be driven into resource exhaustion that degrades or halts the service. No public exploit code has been identified at time of analysis and it is not listed in CISA KEV; SSVC records Exploitation: none with Automatable: yes, indicating a technically reproducible, wormable-class DoS pattern rather than a currently observed campaign. Impact is limited to availability - no confidentiality or integrity loss and no code execution path.

RemediationAI

Apply the vendor patch: a fix is available from Microsoft per the MSRC update guide (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-96960). Windows Update or the .NET Framework servicing updates will bring affected framework builds up to the fixed versions - .NET Framework 4.8 to 4.8.4811.0 or later, 4.8.1 to 4.8.9363.0 or later, 3.5 to 2.0.50727.9188 / 3.0.30729.9171 or later, and 4.6.2/4.7/4.7.1/4.7.2 to 4.7.4150.0 or later - while applications consuming the standalone library must move from System.Security.Cryptography.Xml 10.0.0 to 10.0.13 or newer. Where patching must be staged, compensating controls for the DoS exposure are to disable XML signature verification or XML parsing endpoints that accept anonymous/untrusted input until the update lands (accepting loss of signed-XML functionality), to cap request body size and pre-parse XML nesting depth/node count at the reverse proxy or HTTP server (rejecting oversized documents; may break legitimate large signed payloads), and to apply per-endpoint rate limiting or connection throttling to blunt amplification (which reduces but does not eliminate exhaustion on a single crafted request). Because the assessed impact is availability-only with no code execution or data disclosure, patching can be prioritized against internet-facing XML/SAML/SOAP services above internal-only hosts; note that SSVC marks the vulnerability as Automatable: yes, so exposed unpatched endpoints remain readily testable by attackers.

Affected VersionsENISA

Microsoft .NET Framework 4.8 4.8.0 <4.8.4811.0
System.Security.Cryptography.Xml 10.0.0 <10.0.13
Microsoft .NET Framework 3.5 AND 4.7.2 4.7.0 <2.0.50727.9073 AND 3.0.30729.9070 AND 4.7.4150.0
Microsoft .NET Framework 3.5 AND 4.8 4.8.0 <2.0.50727.9073 AND 3.0.30729.9070 AND 4.8.4811.0
Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 3.0.0.0 <2.0.50727.8987 AND 3.0.30729.8982 AND 4.7.4150.0
Microsoft .NET Framework 3.5 3.5.0 <2.0.50727.9188 AND 3.0.30729.9171
Microsoft .NET Framework 3.5 AND 4.8.1 4.8.1 <2.0.50727.9188 AND 3.0.30729.9171 AND 4.8.9363.0
Microsoft .NET Framework 4.8.1 4.8.0.0 <4.8.9363.0
Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2 4.7.0 <4.7.4150.0

Affected Packages

nuget system.security.cryptography.xml fix: 8.0.5, 9.0.21, 10.0.13, 11.0.0-rc.2
euvd microsoft_net_framework_4_6_2_4_7_4_7_1_4_7_2 fix: 4.7.4150.0
euvd microsoft_net_framework_4_8 fix: 4.8.4811.0
euvd microsoft_net_framework_4_8_1 fix: 4.8.9363.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 4 packages in nuget, 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 class is CWE-405, Asymmetric Resource Consumption (Amplification): the attacker expends a small amount of input while the victim application expends disproportionate CPU, memory, or I/O, typically through pathological XML such as deeply nested elements, oversized signature structures, or canonicalization/transformation chains that the parser expands far more than the payload size suggests. The affected technology is the XML digital-signature stack used for WS-Security, SAML assertions, SOAP endpoints, and signed-document validation: System.Security.Cryptography.Xml in .NET (SignedXml and associated canonicalization/transform classes) plus the .NET Framework builds that ship it. Per EUVD, affected versions span .NET Framework 3.5, 4.6.2/4.7/4.7.1/4.7.2, 4.8 before 4.8.4811.0, 4.8.1 before 4.8.9363.0, and the standalone System.Security.Cryptography.Xml package before 10.0.13. Consistent with the assessed vector (PR:N/UI:N/AV:N), no authentication, user interaction, or special configuration is needed once such an endpoint is network-reachable; the practical reachability limit is that the application must actually cryptographically process externally supplied XML. Note that the single NVD reference points to the Microsoft Update Guide for this CVE, which is the authoritative source for version-specific fixes.

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

Vendor (microsoft) PRIMARY 7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
ENISA EUVD HIGH
vuln.today AI 7.5 HIGH

Network-reachable, low-complexity, unauthenticated amplification DoS (CWE-405) with no user interaction and availability-only impact, so C:N/I:N/A:H and S:U.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

2
Patch available
Oct 13, 2026 - 20:20 EUVD
CVE Published
Oct 13, 2026 - 19:22 cve.org
HIGH 7.5

DescriptionCVE.org

Asymmetric resource consumption (amplification) in .NET allows an unauthorized attacker to deny service over a network.

Technical POC Analysis

No runnable PoC was supplied with this advisory, and no patch diff is present in the evidence.

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Executive ViewAI

Why It Matters

Microsoft .NET Framework and System.Security.Cryptography.Xml are vulnerable to an unauthenticated remote denial-of-service that can exhaust server resources, potentially disrupting critical business applications and services that rely on XML processing. This high-severity flaw affects a wide range of .NET versions, and while no public exploit identified at time of analysis, the automated nature of the attack pattern raises concerns for internet-facing services. Leadership should prioritize patching to maintain availability of customer-facing and internal systems.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
1.1%
Top 36% exploitable
Prevalence
Ubiquitous
.NET Framework runtime ships with and underpins nearly all Windows environments
Threat Intel
2
1 sources
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Less Likely
Data Quality
7 sources
Confidence: High

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 1.1%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: +5

More in .NET

View all
CVE-2026-87697 HIGH POC
8.8 Oct 13

Remote code execution affects Windows desktop applications built on the Microsoft.WindowsDesktop.App.Runtime (WPF) compo

CVE-2023-7334 CRITICAL POC
9.8 Jan 15

Changjetong T+ (through 16.x) has .NET deserialization RCE in an AjaxPro endpoint. Attacker-controlled JSON triggers des

CVE-2026-75513 CRITICAL POC
9.1 Sep 16

SQL injection (CWE-89) in Marten, the .NET transactional document DB and event store for PostgreSQL, affects versions 7.

CVE-2026-100369 HIGH POC
8.4 Sep 25

Argument injection in the CliInvoke .NET process-wrapping library (and its former identity, AlastairLundy.CliInvoke) all

CVE-2019-25359 HIGH POC
8.2 Feb 18

SD.NET RIM versions before 4.7.3c contain a SQL injection vulnerability that allows attackers to inject malicious SQL st

CVE-2026-25925 HIGH POC
7.8 Feb 09

PowerDocu versions prior to 2.4.0 allow arbitrary .NET object instantiation and code execution through unsafe deserializ

CVE-2025-24070 HIGH POC
7.0 Mar 11

Weak authentication in ASP.NET Core &amp; Visual Studio allows an unauthorized attacker to elevate privileges over a net

CVE-2026-26282 MEDIUM POC
6.6 Feb 19

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

CVE-2026-27709 MEDIUM POC
6.6 Feb 26

Out-of-bounds memory read in NanaZip versions 5.0.1252.0 through 6.0.1637.x allows local authenticated attackers to disc

CVE-2020-37103 MEDIUM POC
6.4 Feb 03

DotNetNuke 9.5 contains a persistent cross-site scripting vulnerability that allows normal users to upload malicious XML

CVE-2026-3263 MEDIUM POC
6.3 Feb 26

Asp.Net-Core-Inventory-Order-Management-System versions up to 9.20250118. contains a security vulnerability (CVSS 6.3).

CVE-2025-54539 CRITICAL
9.8 Oct 16

Remote code execution in the ActiveMQ NMS AMQP .NET client affects all releases up to and including 2.3.0 when the clien

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy