dbcve.org
Asp.net CoreApplication · Microsoft

CVE-2026-26130

HIGH · 7.5 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 8.0.25 / 9.0.14 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Allocation of resources without limits or throttling in ASP.NET Core allows an unauthorized attacker to deny service over a network.

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 confidence

ASP.NET Core is vulnerable to a network denial-of-service attack due to insufficient resource allocation limits or throttling. An unauthenticated attacker can consume excessive resources by sending requests that trigger unbounded allocation, potentially exhausting server resources and making the application unavailable.

MitigationImplement request throttling, connection limits, and resource quotas in ASP.NET Core using built-in rate limiting middleware or custom middleware to restrict resource consumption per client.

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
Asp.net CoreApplication
Affected:>= 8.0.0, < 8.0.25>= 9.0.0, < 9.0.14>= 10.0.0, < 10.0.4

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed ASP.NET Core runtime version
    Run `dotnet --list-runtimes` or check the Microsoft.AspNetCore.App.Runtime entry in your deployment
    Affected if The runtime version falls within 8.0.0-8.0.24, 9.0.0-9.0.13, or 10.0.0-10.0.3
  2. Verify if rate-limiting middleware is registered
    Inspect your Startup.cs or Program.cs for calls to `app.UseRateLimiter()` or custom throttling middleware
    Affected if No rate-limiting middleware is configured and the ASP.NET Core version is in the affected range
  3. Check Kestrel server limit configuration
    Review your appsettings.json or Program.cs for Kestrel endpoint configuration, specifically looking for any Limit or MaxConnections settings
    Affected if Kestrel has no explicit connection or request limits configured and the version is affected
  4. Confirm absence of custom request throttling
    Search project code for any custom logic that constrains requests per client (e.g., per-IP limits, token bucket implementations)
    Affected if No custom or built-in throttling mechanism exists and the version is vulnerable

You are affected if your ASP.NET Core runtime version is 8.0.0-8.0.24, 9.0.0-9.0.13, or 10.0.0-10.0.3 AND no request throttling, connection limits, or resource quotas are configured in your application.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 8.0.25 / 9.0.14 / 10.0.4 or later
Fixed in 8.0.259.0.1410.0.4
Interim mitigation

Implement request throttling, connection limits, and resource quotas in ASP.NET Core using built-in rate limiting middleware or custom middleware to restrict resource consumption per client.

Recommended fix High confidence

Upgrade to .NET 8.0.25+, .NET 9.0.14+, or .NET 10.0.4+ depending on your major version

  1. Identify your current ASP.NET Core version by checking the .csproj file or running dotnet --version
  2. For .NET 8.x projects: Update the Microsoft.AspNetCore.App framework reference or NuGet packages to version 8.0.25 or later
  3. For .NET 9.x projects: Update the Microsoft.AspNetCore.App framework reference or NuGet packages to version 9.0.14 or later
  4. For .NET 10.x projects: Update the Microsoft.AspNetCore.App framework reference or NuGet packages to version 10.0.4 or later
  5. After updating, run dotnet restore and dotnet build to verify dependencies resolve correctly
  6. Run existing unit and integration tests to verify application functionality is preserved
  7. Deploy to a staging environment and perform load testing to verify the resource limiting fix works as expected
Caveat Minor version updates typically have minimal breaking changes, but test thoroughly as with any framework update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Asp.net Core Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-26130 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-26130 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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