Skip to main content
Development 2 min read 289 views

.NET Denial-of-Service Vulnerability CVE-2026-26127 Affects Applications on All Platforms

A newly disclosed vulnerability in Microsoft's .NET runtime (CVE-2026-26127) allows attackers to remotely crash .NET 9.0 and 10.0 applications on Windows, macOS, and Linux — affecting web APIs, microservices, and cloud-native applications built on the framework.

TD

TechDrop Editorial

Share:

CVE-2026-26127, disclosed as part of Microsoft's March 2026 Patch Tuesday, is a denial-of-service vulnerability in the .NET runtime that allows attackers to remotely crash .NET 9.0 and 10.0 applications on Windows, macOS, and Linux — affecting web APIs, microservices, and cloud-native applications built on the framework.

Vulnerability Details

The flaw exists in .NET's HTTP request processing pipeline, where a specially crafted request can trigger an unhandled exception that crashes the application process. The vulnerability is particularly impactful for web-facing .NET applications because it can be triggered by a single malicious HTTP request, requires no authentication, and causes a complete process crash rather than a graceful error response. Applications running behind load balancers may recover automatically as new instances are spawned, but the crash still causes request loss and potential data corruption for in-flight operations.

Affected Platforms

The vulnerability affects .NET 9.0 and the preview release of .NET 10.0 across all supported platforms — Windows, macOS, and Linux. This cross-platform impact means that the vulnerability is relevant regardless of the deployment target, affecting applications running in Docker containers, Kubernetes pods, Azure App Services, and traditional server deployments equally. The .NET team has released patches for both affected versions, and NuGet package updates are available for projects that reference the affected runtime components directly.

Mitigation

Organizations running .NET 9.0 or 10.0 applications should apply the March 2026 runtime update immediately. For applications that cannot be immediately updated, Web Application Firewalls (WAFs) can be configured to block the specific request patterns that trigger the vulnerability, though Microsoft has not published the precise trigger patterns to avoid aiding exploitation. Organizations should also review their application restart and health check configurations to ensure that crashed applications are automatically restarted and that health probes detect the crash condition quickly.

Related Articles