DEV Community

CVE Reports
CVE Reports

Posted on Originally published at cvereports.com

CVE-2026-109478: CVE-2026-109478: Algorithmic Complexity Denial of Service in ASP.NET Core Header Parsing

CVE-2026-109478: Algorithmic Complexity Denial of Service in ASP.NET Core Header Parsing

Vulnerability ID: CVE-2026-109478
CVSS Score: 7.5
Published: 2026-11-11

CVE-2026-109478 is a network-accessible Denial of Service (DoS) vulnerability in ASP.NET Core caused by inefficient algorithmic complexity (CWE-407) when parsing comma-separated HTTP request headers. Prior to the patch, the internal helper method ParsingHelpers.GetHeaderSplit repeatedly called StringValues.Concat inside a loop iterating over each comma-separated token. Because StringValues allocates a new array of size k + 1 and copies all existing elements upon each concatenation, processing N tokens incurs O(N^2) time and space complexity. An unauthenticated remote attacker can send HTTP requests with headers containing thousands of short, comma-separated values to exhaust CPU cycles and induce severe Garbage Collection (GC) pauses, rendering the web application unresponsive.

TL;DR

An O(N^2) algorithmic complexity flaw in ASP.NET Core's ParsingHelpers.GetHeaderSplit method allows unauthenticated remote attackers to cause a Denial of Service via crafted HTTP headers packed with comma-separated tokens. Fixed in .NET 8.0.34 and .NET 9.0.0-preview.4.24266.19.


Technical Details

  • Vulnerability ID: CVE-2026-109478
  • Weakness Class: CWE-407 (Inefficient Algorithmic Complexity)
  • Affected Component: Microsoft.AspNetCore.Http.Abstractions (ParsingHelpers.GetHeaderSplit)
  • Attack Vector: Network (Unauthenticated HTTP Request Headers)
  • CVSS v3.1 Score: 7.5 HIGH (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)
  • Primary Impact: Application Denial of Service (CPU & GC Exhaustion)
  • Exploit Status: Unproven (No Public PoC / Not in CISA KEV)
  • Patched In: .NET 8.0.34 / .NET 9.0.0-preview.4.24266.19

Affected Systems

  • Microsoft .NET 8.0 (Linux, macOS, Windows)
  • Microsoft .NET 9.0 (Linux, macOS, Windows)
  • Microsoft Visual Studio 2022 (Windows)
  • Microsoft Visual Studio 2026 (Windows)
  • .NET 8.0: >= 8.0.0, < 8.0.34 (Fixed in: 8.0.34)
  • .NET 9.0: >= 9.0.0, < 9.0.0-preview.4.24266.19 (Fixed in: 9.0.0-preview.4.24266.19)
  • Visual Studio 2022: >= 17.14.0, < 17.14.45 (Fixed in: 17.14.45)
  • Visual Studio 2026: >= 18.11.0, < 18.11.4 (Fixed in: 18.11.4)
  • Visual Studio 2026: == 18.12.0 (Fixed in: 18.12.1)

Code Analysis

Commit: 2523887

Replace StringValues.Concat loop in ParsingHelpers.GetHeaderSplit with ValueListBuilder in release/8.0 branch.

File: src/Http/Http.Abstractions/src/Extensions/HeaderDictionaryExtensions.cs
@@ -43,7 +43,7 @@ public static string[] GetCommaSeparatedValues(this IHeaderDictionary headers, s
     {
         // GetHeaderSplit will return only non-null elements of the given IHeaderDictionary.
 #pragma warning disable CS8619 // Nullability of reference types in value doesn't match target type.
-        return ParsingHelpers.GetHeaderSplit(headers, key).ToArray();
+        return ParsingHelpers.GetHeaderSplit(headers, key);
 #pragma warning restore CS8619 // Nullability of reference types in value doesn't match target type.
     }

File: src/Http/Http.Abstractions/src/Internal/ParsingHelpers.cs
@@ -14,11 +14,11 @@ public static StringValues GetHeader(IHeaderDictionary headers, string key)
         return headers.TryGetValue(key, out value) ? value : StringValues.Empty;
     }

-    public static StringValues GetHeaderSplit(IHeaderDictionary headers, string key)
+    public static string[] GetHeaderSplit(IHeaderDictionary headers, string key)
     {
         var values = GetHeaderUnmodified(headers, key);

-        StringValues result = default;
+        ValueListBuilder<string> strings = new([null!, null!, null!, null!]);

         foreach (var segment in new HeaderSegmentCollection(values))
         {
@@ -27,11 +27,14 @@ public static StringValues GetHeaderSplit(IHeaderDictionary headers, string key)
                 var value = DeQuote(segment.Data.Value);
                 if (!string.IsNullOrEmpty(value))
                 {
-                    result = StringValues.Concat(in result, value);
+                    strings.Add(value);
                 }
             }
         }

+        string[] result = strings.AsSpan().ToArray();
+        strings.Dispose();
+
         return result;
     }
Enter fullscreen mode Exit fullscreen mode

Commit: effb34d

Original fix commit in main branch optimizing ParsingHelpers.GetHeaderSplit using ValueListBuilder.

Mitigation Strategies

  • Upgrade the ASP.NET Core Runtime and SDK to the latest patched versions (.NET 8.0.34 or .NET 9.0.0-preview.4.24266.19+).
  • Rebuild and redeploy any self-contained ASP.NET Core applications or containers that bundle Microsoft.AspNetCore.Http.Abstractions.dll.
  • Constrain Kestrel's MaxRequestHeaderFieldSize and MaxRequestHeadersTotalSize configuration properties to limit the maximum number of tokens an attacker can pack into a single HTTP request.
  • Deploy Web Application Firewall (WAF) or reverse proxy rules at the perimeter to inspect and block HTTP headers containing excessive comma-separated segments.

Remediation Steps:

  1. Inventory all servers, virtual machines, and container images running .NET 8.0 (< 8.0.34) or .NET 9.0 (< 9.0.0-preview.4.24266.19).
  2. Download and install the patched ASP.NET Core Runtime and .NET SDK packages from Microsoft (version 8.0.34 for .NET 8 environments).
  3. Update Visual Studio build environments to version 17.14.45 (VS 2022) or 18.11.4 / 18.12.1+ (VS 2026).
  4. For framework-dependent deployments, restart the hosting service (IIS, systemd service, or container pod) after installing the host runtime update.
  5. For self-contained deployments and Docker images, update base images (e.g., mcr.microsoft.com/dotnet/aspnet:8.0.34), recompile the application, and redeploy.
  6. Monitor .NET runtime performance counters (% Time in GC, Gen 2 Collection Rate, and LOH Size) post-deployment to verify normal memory allocation behavior.

References


Read the full report for CVE-2026-109478 on our website for more details including interactive diagrams and full exploit analysis.

Top comments (0)