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-58280 Overview
CVE-2026-58280 is an uncontrolled recursion vulnerability in Microsoft .NET that enables an unauthenticated attacker to cause a denial of service over a network. The flaw is tracked under CWE-674: Uncontrolled Recursion and affects applications that process attacker-supplied input through recursive .NET code paths. Successful exploitation exhausts stack or compute resources on the target process, forcing it to crash or become unresponsive. No authentication or user interaction is required, and the attack can be launched remotely across the network.
Critical Impact
Remote, unauthenticated attackers can trigger service outages in .NET workloads without credentials or user interaction.
Affected Products
- Microsoft .NET (refer to the Microsoft Security Update CVE-2026-58280 advisory for the complete list of affected versions)
- Applications and services built on vulnerable .NET runtime versions
- Internet-exposed .NET endpoints that parse untrusted input
Discovery Timeline
- 2026-10-13 - CVE-2026-58280 published to the National Vulnerability Database (NVD)
- 2026-10-13 - Microsoft publishes security update guidance for CVE-2026-58280
- 2026-10-13 - Last updated in NVD database
Technical Details for CVE-2026-58280
Vulnerability Analysis
The vulnerability stems from uncontrolled recursion within .NET code paths that process attacker-controlled input. When a function invokes itself without an enforced termination condition or depth limit, each recursive call consumes additional stack memory. Attackers submit crafted input that drives recursion to the point where the process stack is exhausted. The resulting StackOverflowException cannot be caught reliably in managed code and terminates the host process. For long-running services such as web applications, APIs, and background workers, this converts a single malicious request into a service outage. The impact is limited to availability; confidentiality and integrity are not affected.
Root Cause
The root cause is a missing or ineffective recursion depth check in a .NET component [CWE-674]. Input parsing or data structure traversal functions descend recursively based on properties of the input rather than a bounded iteration. Microsoft has not published full implementation details beyond the advisory listed in the Microsoft Security Update CVE-2026-58280 entry.
Attack Vector
The attack vector is network-based and requires no privileges or user interaction. An attacker sends a specially crafted payload, such as a deeply nested document, serialized object, or protocol message, to a .NET service that exposes the vulnerable parser. The .NET runtime recurses until the stack is exhausted and the worker process terminates. Repeated requests sustain the denial of service. See the Microsoft advisory for product-specific exploitation prerequisites.
Detection Methods for CVE-2026-58280
Indicators of Compromise
- Repeated StackOverflowException events or sudden worker process terminations in Windows Event Logs and application logs.
- Spikes of oversized or deeply nested payloads reaching .NET-based endpoints such as ASP.NET, WCF, or custom TCP services.
- Elevated restart counts for IIS application pools, Kestrel workers, or Windows services hosting .NET code.
Detection Strategies
- Monitor crash telemetry for unmanaged exceptions and correlate with inbound request patterns from a single source.
- Inspect request bodies at the edge for excessive nesting depth in JSON, XML, or serialized formats before they reach application code.
- Alert on short-interval repeated crashes of the same .NET process, which indicates automated exploitation attempts.
Monitoring Recommendations
- Forward Windows Error Reporting, IIS, and application logs to a central SIEM for pattern analysis across hosts.
- Track application pool recycle events and unhandled exception counters as availability signals.
- Baseline normal request payload sizes and nesting depths so anomalous traffic surfaces quickly.
How to Mitigate CVE-2026-58280
Immediate Actions Required
- Apply the Microsoft security updates referenced in the Microsoft Security Update CVE-2026-58280 advisory to all affected .NET runtimes and SDKs.
- Inventory internet-exposed services built on .NET and prioritize patching for public-facing workloads.
- Restart application pools and services after patching to ensure the updated runtime loads.
Patch Information
Microsoft has released updates addressing CVE-2026-58280. Administrators should consult the Microsoft Security Update Guide entry for the specific .NET versions, KB numbers, and installation guidance that apply to their environment. Container images and self-contained deployments must be rebuilt against the patched runtime.
Workarounds
- Place a web application firewall or reverse proxy in front of .NET services and enforce maximum request size and nesting depth limits.
- Configure deserializers and parsers with explicit depth limits, for example JsonSerializerOptions.MaxDepth for System.Text.Json.
- Rate-limit anonymous requests to parsing endpoints to reduce the impact of repeated exploitation attempts until patches are deployed.
# Configuration example: enforce JSON depth limits in ASP.NET Core
# Program.cs
builder.Services.Configure<JsonOptions>(options =>
{
options.SerializerOptions.MaxDepth = 32;
});
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

