Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify endpoint accepting form data
-
DeliverySend incrementally chunked form body
-
ExploitTrigger repeated full-buffer rescans in FormPipeReader
-
ExecutionDrive quadratic CPU consumption
-
ImpactExhaust server resources, deny service
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V2 - Validation and Business Logic Algorithmic complexity limits
|
| Exploitation Conditions | Exploitation requires a reachable ASP.NET Core application endpoint that accepts and parses HTTP form data via Microsoft.AspNetCore.WebUtilities FormPipeReader, running an affected runtime (8.0.0-8.0.31, 9.0 before 9.0.21, or 10.0 before 10.0.13). The attacker must deliver the form body incrementally (e.g., many small chunks) so the parser repeatedly rescans the full buffered body, producing quadratic CPU cost. Limiting factors: only applications that process form submissions are exposed; impact is confined to availability (no data disclosure or modification); and the required incremental-delivery technique is reflected in the AC:H rating, making trivial single-request abuse less likely. No authentication is required (PR:N). |
| Impact | This is a genuine but moderate-priority issue. The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H, score 5.9) describes a network-reachable, unauthenticated flaw with impact limited to availability only - consistent with the CWE-407 algorithmic-complexity denial of service in Microsoft.AspNetCore.WebUtilities FormPipeReader. The signals are internally consistent rather than conflicting: AC:H reflects that the attacker must deliver form data in an incremental/chunked manner to trigger quadratic CPU consumption, and the CISA SSVC decision framework corroborates a lower urgency (Exploitation: none, Automatable: no, Technical Impact: partial). No EPSS score, CISA KEV listing, or public POC was provided in the intelligence set, so there is no evidence of real-world exploitation - this is a high-impact-ceiling (A:H) but availability-only, moderate-severity issue, not a critical priority. Note one data-quality concern: the input Tags label this 'Authentication Bypass', which directly contradicts the description, CWE-407, and the vendor GHSA advisory (all of which describe a denial of service with no confidentiality or integrity impact) - the tag appears mislabeled and should not drive triage. SSVC 'Automatable: no' plus AC:H suggests any exploitation would be deliberate and targeted rather than mass/wormable. |
| Exploit ScenarioDerived | An unauthenticated remote attacker identifies an ASP.NET Core endpoint that accepts form submissions and sends a form body delivered in many small increments, causing FormPipeReader to repeatedly rescan the full buffered body. The resulting quadratic CPU consumption exhausts server processing capacity and denies service to legitimate users. No public exploit code was identified at time of analysis, and the attack requires specific incremental delivery (reflected in CVSS AC:H). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
A denial-of-service condition in ASP.NET Core allows an unauthenticated, remote attacker to exhaust server CPU by submitting HTTP form data in many small increments, causing Microsoft.AspNetCore.WebUtilities FormPipeReader to repeatedly rescan the entire buffered request body. The flaw (CWE-407, inefficient algorithmic complexity) affects applications running ASP.NET Core 8.0.0-8.0.31, 9.0 before 9.0.21, and 10.0 before 10.0.13, as well as Microsoft Visual Studio 2022 17.14 before 17.14.42 and Visual Studio 2026 18.10 before 18.10.4, and carries a CVSS 3.1 base score of 5.9 (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H). Only availability is impacted - there is no data disclosure or modification - and the high attack-complexity rating reflects the need for an incrementally delivered body rather than a single malformed request. No public exploit code and no confirmed active exploitation have been identified at time of analysis, and CISA's SSVC assessment records Exploitation: none, Automatable: no, Technical Impact: partial.
RemediationAI
Vendor-released patches are available: upgrade ASP.NET Core to 8.0.32, 9.0.21, or 10.0.13 respectively (the matching Microsoft.AspNetCore.App.Runtime.* NuGet packages at those versions), and update Microsoft Visual Studio 2022 to 17.14.42 or Visual Studio 2026 to 18.10.4 if the tooling runtime is used in exposed scenarios; full details and download links are in the MSRC update guide (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-70196), the GitHub security advisory GHSA-57xr-hfxx-jw5x (https://github.com/dotnet/aspnetcore/security/advisories/GHSA-57xr-hfxx-jw5x), and the .NET announcement (https://github.com/dotnet/announcements/issues/465). Where immediate patching is not possible, compensating controls should target the incremental-body delivery required for exploitation: enforce a strict Kestrel request body size limit (MaxRequestBodySize) to cap how much data can be buffered and re-scanned, accepting that legitimate large uploads will be rejected and limits must be tuned per endpoint; set MinRequestBodyDataRate/MinResponseDataRate so slow, drip-fed bodies are timed out before the quadratic cost accumulates, at the risk of dropping clients on poor networks; apply ASP.NET Core rate limiting or per-IP concurrency limits at the edge to throttle chunked submissions, which adds latency and can be evaded by distributed sources; and terminate TLS/buffering at a reverse proxy that reads the whole body before forwarding, trading memory and latency on the proxy for deterministic parsing - the proxy itself must then be sized for full-body buffering. Environments that only serve JSON or other non-form APIs can disable form parsing and multipart model binding on affected endpoints as a low-cost interim measure. Prioritize patching any internet-facing service that accepts form submissions.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 17 packages in nuget, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is FormPipeReader within the Microsoft.AspNetCore.WebUtilities package, the low-level reader that ASP.NET Core uses when model-binding form-encoded and multipart request bodies. Because the reader buffers incoming body bytes and re-parses the accumulated buffer as new data arrives, an attacker who fragments a form submission into numerous small chunks forces the parser to restart parsing over already-seen data on every chunk, producing quadratic (O(n²)) CPU consumption relative to body size. This places the issue in the CWE-407 class, inefficient algorithmic complexity, rather than in memory-corruption or injection territory, which is why the CVSS vector shows only Availability: High with Confidentiality and Integrity unchanged. Affected code is distributed both as the shared framework/runtime (Microsoft.AspNetCore.App.Runtime.* NuGet packages, split per RID: linux-arm, linux-arm64, linux-musl-arm, linux-musl-arm64, linux-musl-x64, linux-x64, osx-arm64, osx-x64, win-arm, win-x64, etc.) and as the runtime bundled into Microsoft Visual Studio tooling. It affects Windows, Linux, and macOS on all architectures where form parsing is reachable. Note that one supplied tag labels the issue 'Authentication Bypass'; nothing in the vendor advisory, the CWE mapping, or the assessed vector supports an authentication bypass - the correct characterization is an unauthenticated (PR:N) resource-exhaustion denial of service.
Know when Asp Net Core gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Network-reachable and unauthenticated (AV:N/PR:N); AC:H because the attacker must craft incremental form delivery to trigger the quadratic path; availability-only impact (A:H), no C/I.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Inefficient algorithmic complexity in ASP.NET Core allows an unauthorized attacker to deny service over a network.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
More in Asp Net Core
View allDenial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
.NET and Visual Studio Denial of Service Vulnerability. Rated high severity (CVSS 7.5), this vulnerability is remotely e
Allocation of resources without limits or throttling in ASP.NET Core allows an unauthorized attacker to deny service ove
ASP.NET Core Kestrel request smuggling allows a low-privileged network attacker (PR:L, no user interaction) to desynchro
Decompression bomb (CWE-409) in ASP.NET Core allows unauthenticated remote attackers to exhaust server resources and den
ASP.NET Core 2.0 allows an attacker to steal log-in session information such as cookies or authentication tokens via a s
Request smuggling in the ASP.NET Core Kestrel HTTP/1 server lets a remote, unauthenticated attacker desynchronize HTTP r
Cross-site scripting (CWE-79) in the ASP.NET Core Blazor WebAssembly Server hosting component allows an unauthenticated,
Account takeover is possible in applications built on ASP.NET Core Identity because the framework's password-reset and e
ASP.NET Core 1.0, 1.1, and 2.0 allow an attacker to bypass Cross-origin Resource Sharing (CORS) configurations and retri
Remote denial of service in ASP.NET Core enables unauthenticated network attackers to exhaust server resources and disru
ASP.NET Core and Visual Studio Elevation of Privilege Vulnerability. Rated high severity (CVSS 8.8), this vulnerability
EUVD-2026-99695
GHSA-57xr-hfxx-jw5x
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB