Skip to main content
Vulnerability Database/CVE-2026-70181

CVE-2026-70181: ASP.NET Core DOS Vulnerability

CVE-2026-70181 is a denial of service vulnerability in ASP.NET Core caused by allocation of resources without limits or throttling. Attackers can exploit this flaw over a network to deny service. This article covers technical details, affected versions, impact assessment, and mitigation strategies.

Published:

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-70181 Overview

CVE-2026-70181 is a denial of service vulnerability in ASP.NET Core caused by allocation of resources without limits or throttling [CWE-770]. An unauthorized remote attacker can send crafted network requests that force the application to consume excessive resources, degrading or halting availability. The flaw requires no authentication and no user interaction, making it reachable by any client that can connect to an exposed ASP.NET Core service.

Critical Impact

Unauthenticated remote attackers can exhaust server resources and deny service to legitimate users of any affected ASP.NET Core application reachable over the network.

Affected Products

  • ASP.NET Core (see Microsoft Security Update CVE-2026-70181 for impacted versions)
  • Applications hosting ASP.NET Core middleware exposed over a network
  • Services built on affected ASP.NET Core runtime components

Discovery Timeline

  • 2026-10-13 - CVE CVE-2026-70181 published to NVD
  • 2026-10-13 - Last updated in NVD database

Technical Details for CVE-2026-70181

Vulnerability Analysis

The vulnerability is categorized under [CWE-770]: Allocation of Resources Without Limits or Throttling. ASP.NET Core processes certain network-reachable inputs without enforcing bounds on the resources it allocates to handle them. An attacker can exploit this behavior by issuing requests that trigger disproportionate memory, CPU, or thread consumption on the server.

Because the attack targets availability only, successful exploitation does not disclose data or alter state. The impact is denial of service to all users of the affected process until the condition is cleared or the service is restarted. Microsoft tracks the issue in its Security Update Guide; refer to the Microsoft advisory for the authoritative list of affected builds.

Root Cause

The root cause is missing enforcement of upper bounds on resources allocated during request handling. When input-driven allocation lacks caps, quotas, or throttling, a single client can scale server-side cost arbitrarily. This is a classic resource exhaustion pattern that commonly surfaces in parsers, buffer pools, connection handlers, and queueing layers.

Attack Vector

The attack vector is network based. An unauthenticated attacker sends crafted requests to an exposed ASP.NET Core endpoint. Repeated or malformed payloads inflate server-side allocations until memory, CPU, or thread pools are exhausted. No credentials, no user interaction, and no prior foothold are required.

No public proof-of-concept exploit is listed in the available references. The vulnerability is not currently tracked on the CISA Known Exploited Vulnerabilities catalog. The EPSS probability sits at 1.056% (63.78 percentile) as of 2026-10-15.

Detection Methods for CVE-2026-70181

Indicators of Compromise

  • Sudden spikes in memory, CPU, or thread pool consumption on ASP.NET Core worker processes without a corresponding business workload change.
  • Elevated HTTP request rates from a narrow set of source IPs or user agents to specific endpoints.
  • Repeated application restarts, Kestrel socket exhaustion, or OutOfMemoryException entries in application logs.

Detection Strategies

  • Baseline normal request volume, size, and latency per endpoint, then alert on statistical outliers that correlate with resource growth.
  • Instrument ASP.NET Core with runtime metrics (GC heap size, thread count, queued requests) and forward to a SIEM for correlation.
  • Inspect reverse proxy and WAF logs for request patterns consistent with resource amplification against affected endpoints.

Monitoring Recommendations

  • Monitor dotnet-counters metrics such as working-set, gc-heap-size, and threadpool-queue-length on hosts running ASP.NET Core.
  • Track Kestrel connection counts and HTTP/2 stream counts per client to identify abusive peers.
  • Alert on process crashes and automatic app pool recycles that align with inbound traffic spikes.

How to Mitigate CVE-2026-70181

Immediate Actions Required

  • Apply the ASP.NET Core security updates published in the Microsoft Security Update Guide as soon as they are available for your runtime version.
  • Inventory all services built on ASP.NET Core and prioritize internet-exposed workloads for patching.
  • Place a rate-limiting layer in front of exposed endpoints until patches are deployed.

Patch Information

Microsoft has published guidance for CVE-2026-70181 in the Security Update Guide. Administrators should consult the Microsoft advisory for fixed package versions of the ASP.NET Core runtime and NuGet packages, then upgrade affected applications and redeploy. Confirm the runtime version in use with dotnet --info after patching.

Workarounds

  • Enable ASP.NET Core rate limiting middleware to cap concurrent requests and queue length per client.
  • Configure Kestrel server limits such as MaxConcurrentConnections, MaxRequestBodySize, and request header size caps.
  • Deploy a web application firewall or reverse proxy to enforce request size, rate, and connection limits upstream of the application.
  • Restrict exposure of non-public ASP.NET Core services to trusted networks via firewall rules until patched.
bash
# Example Kestrel limits in appsettings.json
{
  "Kestrel": {
    "Limits": {
      "MaxConcurrentConnections": 1000,
      "MaxConcurrentUpgradedConnections": 100,
      "MaxRequestBodySize": 10485760,
      "MaxRequestHeadersTotalSize": 32768,
      "KeepAliveTimeout": "00:02:00"
    }
  }
}

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

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.