ASP.NET Core Comma-Separated Header Parsing Denial of Service
CVE-2026-109478 is an algorithmic-complexity vulnerability in ASP.NET Core HTTP header parsing. ParsingHelpers.GetHeaderSplit, exposed through HeaderDictionaryExtensions.GetCommaSeparatedValues, repeatedly appends parsed tokens using StringValues.Concat. Each append to an array-backed StringValues instance allocates a larger array and copies existing references, producing quadratic copying work and cumulative intermediate allocations. An unauthenticated remote attacker can submit headers containing thousands of small comma-separated values to an application that invokes this parsing path, causing excessive allocation and garbage-collection pressure and potentially denying service. ASP.NET Core 8.0 releases before 8.0.34 are affected; certain .NET 9 preview runtime packages are also identified as affected.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can severely degrade or interrupt application availability through excessive reference copying, intermediate array allocation, and expensive garbage collection. Large intermediate arrays can increase Large Object Heap and Generation 2 collection pressure, causing application pauses. A header containing approximately 15,000 single-character tokens can occupy about 30 KB while inducing approximately 112.5 million reference copies and 900 MB of cumulative intermediate allocations on a 64-bit runtime. No confidentiality or integrity impact is identified.
If you can’t patch tonight, do this now.
Pending patch deployment, reduce individual and aggregate request-header size limits to constrain attacker-controlled token counts and parsing costs. Suggested limits include 4 KB per header and 8 KB across all headers, subject to application compatibility. These restrictions reduce exposure but do not eliminate the vulnerable algorithm and are not a substitute for updating.
Patch, then assume compromise.
Upgrade affected ASP.NET Core 8 runtime packages to version 8.0.34 or a later supported security release. For affected .NET 9 preview runtime packages, the specified fixed version is 9.0.0-preview.4.24267.6. Apply the corresponding vendor or distribution security updates and update independently referenced affected packages, then restart applications. Rebuild and redeploy self-contained applications to replace embedded vulnerable runtimes; machine-wide runtime or SDK updates alone do not update embedded runtimes or standalone package references. The parser fix replaces repeated StringValues concatenation with a geometrically growing ValueListBuilder<string>, pooled intermediate buffers, and a single final output-array allocation.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
17 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.