Unbounded Validation Cache Denial of Service in ASP.NET Core
CVE-2026-118748 is a resource-allocation vulnerability affecting ASP.NET Core in .NET 11 prerelease runtimes. Blazor static server-side rendering client validation retains attacker-controlled form-field names in an unbounded singleton cache. Submissions containing distinct field names can accumulate persistent cache entries across requests, exhausting application-process memory and causing denial of service. Exploitation is network-accessible and requires neither authentication nor user interaction. The vulnerability has a CVSS v3.1 base score of 7.5 and is fixed in ASP.NET Core 11.0.0.
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 eliminate application availability through memory exhaustion. Garbage-collection thrashing, CPU spikes, and prolonged pauses may precede an out-of-memory failure or operating-system termination of the hosting process. Process termination can interrupt concurrent requests, disconnect active WebSocket and SignalR connections, and destroy volatile application state. The assessed impact is confined to availability, with no confidentiality or integrity impact.
If you can’t patch tonight, do this now.
No vendor-confirmed temporary workaround is specified. Potential defense-in-depth measures include bounding caches with capacity limits and eviction, using request-scoped storage where appropriate, rejecting field names that do not correspond to declared model properties, tightening form-field count and key-length limits, limiting request-body size, and applying rate limiting. Request-level limits may reduce exposure but do not necessarily prevent cumulative cache growth across repeated requests; these measures are not substitutes for installing the fix.
Patch, then assume compromise.
Install ASP.NET Core runtime 11.0.0 or a later supported fixed release, and update independently referenced affected runtime packages to a fixed version. Restart affected applications after updating. Rebuild and redeploy self-contained applications with the fixed runtime, because machine-wide runtime updates do not replace embedded runtimes. Updating the SDK alone does not update independently pinned application package references. Red Hat deployments should apply the applicable .NET 11 updates, including RHSA-2026:99054 for RHEL 8 or RHSA-2026:99137 for RHEL 10.
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.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.