CVE-2026-45646
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAllocation of resources without limits or throttling in ASP.NET Core allows an unauthorized attacker to deny service over a network.
In the news
Third-party coverage- Microsoft July 2026 Patch Tuesday fixes massive 570 flaws, 3 zero-days
- Microsoft CVE Summary - Bleeping Computer
Surfaced from public web coverage — external links open in a new tab.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis vulnerability in ASP.NET Core allows attackers to exhaust server resources by allocating resources without proper limits or throttling, enabling network-based denial of service. The lack of resource controls permits unlimited consumption of memory, connections, or other system resources through crafted requests.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 9.5.0< 7.8.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed OData packagesInspect project dependencies or installed NuGet packages for 'Microsoft.AspNetCore.OData' or 'Microsoft.OData.WebApi'. Use 'dotnet list package' in the project directory or check the .csproj file for these package references.Affected if Either package is listed with a version below 9.5.0 (Asp.Net Core OData) or below 7.8.0 (OData Web Api)
-
Check runtime assembly versionsRun 'dotnet list package --include-transitive' to see all OData-related assemblies and their resolved versions, or inspect the bin folder for Microsoft.OData*.dll files and right-click > Properties > Details to view version information.Affected if The OData assembly version shown is less than 9.5.0 or 7.8.0 respectively
-
Verify if application uses OData endpointsExamine the application's Startup.cs or Program.cs for OData route registration (e.g., app.UseODataBatching(), builder.Services.AddOData(), or MapODataRoute). Also check for controllers inheriting from ODataController.Affected if OData routing is registered and the application exposes OData endpoints
-
Inspect request size and resource limits configurationCheck appsettings.json, Program.cs, or Startup.cs for request size limits (e.g., RequestSizeLimit attribute, MaxRequestBodySize), memory limits (MemoryQueueThreshold), or connection limits. Look for AddRequestSizeLimiter or similar throttling middleware.Affected if No explicit request size limits, memory limits, or connection throttling are configured for OData endpoints
-
Review web server resource configurationInspect hosting configuration files (e.g., web.config, appsettings.Development.json) or Kestrel server options for MaxConcurrentConnections, MaxRequestBodySize, or Limits section settings.Affected if Kestrel or IIS server has no configured limits on request body size or concurrent connections
The environment is affected if it runs Microsoft.AspNetCore.OData below version 9.5.0 or Microsoft.OData.WebApi below version 7.8.0 AND lacks explicit resource throttling configuration for OData endpoints.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped7.8.09.5.0
Implement proper resource throttling and limits in ASP.NET Core applications, including request size limits, connection limits, and memory thresholds. Apply available Microsoft security patches for ASP.NET Core and configure appropriate request filtering and rate limiting.
Asp.net Core Odata: upgrade to >= 9.5.0 | Odata Web Api: upgrade to >= 7.8.0
- Identify which affected product is in use: Asp.net Core Odata or Odata Web Api
- For Asp.net Core Odata: Update the Microsoft.AspNetCore.OData NuGet package reference to version 9.5.0 or later
- For Odata Web Api: Update the Microsoft.AspNet.OData NuGet package reference to version 7.8.0 or later
- Run your package manager (NuGet restore) to fetch the updated packages
- Rebuild and test the application to ensure compatibility with the updated library
- Deploy the updated application
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45646 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-45646 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data