Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-96960 Overview
CVE-2026-96960 is a denial-of-service vulnerability in .NET caused by asymmetric resource consumption, also known as an amplification condition. An unauthorized remote attacker can send crafted network input that forces the target process to consume disproportionate server resources. The flaw is tracked under [CWE-405: Asymmetric Resource Consumption (Amplification)]. Microsoft published guidance on October 13, 2026, and no authentication or user interaction is required for exploitation.
Critical Impact
Unauthenticated remote attackers can trigger resource amplification against .NET services, degrading or halting application availability without touching confidentiality or integrity.
Affected Products
- Microsoft .NET (versions specified in Microsoft's advisory)
- Applications and services built on affected .NET runtimes
- Network-exposed .NET workloads processing untrusted input
Discovery Timeline
- 2026-10-13 - CVE CVE-2026-96960 published to the National Vulnerability Database
- 2026-10-13 - Last updated in NVD database
Technical Details for CVE-2026-96960
Vulnerability Analysis
The vulnerability is an amplification-class denial of service in .NET. An attacker transmits a small volume of network input that causes the .NET runtime or framework code to allocate, process, or iterate over a disproportionately large amount of work. The result is an availability-only impact, with no exposure of data confidentiality or integrity, consistent with the vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
Asymmetric resource consumption vulnerabilities typically arise when input size or structure does not bound downstream computation, memory allocation, or I/O. In a server context, repeated malicious requests can starve CPU, memory, or thread-pool resources, forcing the process to drop legitimate traffic or crash.
Microsoft tracks the issue in its security update guide for CVE-2026-96960. See the Microsoft Security Update Guidance for authoritative product and build information.
Root Cause
The root cause is improper bounding of resource consumption relative to attacker-controlled input, classified as [CWE-405]. Input that is cheap to send yields work that is expensive to perform, creating the amplification ratio an attacker needs to exhaust server capacity.
Attack Vector
The attack is executed over a network against any reachable .NET service that processes attacker-supplied input. No credentials, prior access, or user interaction are required. The attacker needs only the ability to send requests to a vulnerable endpoint.
No verified public proof-of-concept code is available at this time. The vulnerability mechanism is described in prose; readers should consult Microsoft's advisory for product-specific technical details.
Detection Methods for CVE-2026-96960
Indicators of Compromise
- Sustained CPU, memory, or thread-pool saturation in .NET worker processes without a corresponding increase in legitimate request volume.
- Spikes in garbage collection activity, allocation rate, or request queue length on .NET application servers.
- Repeated requests from a narrow set of source IPs that produce outsized processing time per request.
Detection Strategies
- Monitor .NET runtime performance counters (% Time in GC, Requests Queued, Threads) for abnormal patterns that correlate with inbound traffic from untrusted sources.
- Correlate web server access logs with application performance telemetry to identify low-byte requests triggering high server-side cost.
- Alert on anomalous ratios between request size and response latency or resource usage per endpoint.
Monitoring Recommendations
- Instrument .NET applications with Application Performance Monitoring to baseline normal resource usage per endpoint.
- Forward web server, load balancer, and runtime telemetry to a centralized analytics platform for cross-source correlation.
- Track source IP reputation and request cardinality for public-facing .NET endpoints.
How to Mitigate CVE-2026-96960
Immediate Actions Required
- Apply the Microsoft security update for CVE-2026-96960 to all affected .NET runtime and SDK installations.
- Inventory applications and container images that bundle .NET runtimes and prioritize patching for internet-facing workloads.
- Enable rate limiting and request size limits on edge proxies and application gateways in front of .NET services.
Patch Information
Microsoft has published patch guidance in the Microsoft Security Update Guidance for CVE-2026-96960. Review the advisory to identify affected .NET versions and apply the corresponding runtime, SDK, and hosting bundle updates. Restart dependent services after patching to load the fixed runtime.
Workarounds
- Place vulnerable .NET services behind a reverse proxy or WAF that enforces per-client request rate limits and connection quotas.
- Reduce request body and header size limits in Kestrel or IIS to constrain attacker input until patches are deployed.
- Restrict network exposure of non-public .NET endpoints using network ACLs or private networking.
# Example: constrain Kestrel limits in appsettings.json to reduce amplification surface
{
"Kestrel": {
"Limits": {
"MaxRequestBodySize": 1048576,
"MaxRequestHeadersTotalSize": 16384,
"MaxConcurrentConnections": 1000,
"MaxConcurrentUpgradedConnections": 100,
"KeepAliveTimeout": "00:00:30",
"RequestHeadersTimeout": "00:00:15"
}
}
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

