CVE-2026-50506
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 is a denial of service vulnerability in ASP.NET Core caused by missing resource limits or throttling controls. An unauthenticated remote attacker can exhaust server resources (memory, CPU, connections) by overwhelming the application with requests, rendering it unavailable to legitimate users.
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.0.0, < 9.5.0>= 7.0.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 package versionRun 'dotnet list package' in the project directory, or inspect the .csproj file for Microsoft.AspNetCore.OData or Microsoft.OData.WebApi package referencesAffected if The package version falls within 7.0.0 to 7.7.x for Microsoft.OData.WebApi, or 9.0.0 to 9.4.x for Microsoft.AspNetCore.OData
-
Confirm OData endpoint routing is enabledInspect Startup.cs or Program.cs for app.UseRouting() followed by app.UseOData() or app.MapODataRoute() calls, and check for OData model configuration in the EDM builderAffected if OData routing is mapped and the application exposes OData endpoints without corresponding rate limiting middleware
-
Verify rate limiting middleware is configuredSearch for app.UseRateLimiter() or [EnableRateLimiting] attributes in Startup.cs, Program.cs, or controller files; also check for RateLimiter options in appsettings.jsonAffected if No rate limiting middleware is registered before OData middleware in the request pipeline
-
Check for resource consumption limitsInspect appsettings.json or appsettings.Development.json for ConsumptionLimits, ThrottlingSettings, or memory/CPU limit configurations specific to ASP.NET Core or the hosting environmentAffected if No throttling or resource consumption limits are defined for the application
The environment is affected if Microsoft.AspNetCore.OData (9.0.0-9.4.x) or Microsoft.OData.WebApi (7.0.0-7.7.x) is installed, OData endpoints are exposed, and no rate limiting middleware or resource consumption limits are configured in the application pipeline.
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.
From vendor data7.8.09.5.0
Implement ASP.NET Core rate limiting middleware to restrict the number of requests per client/IP within a time window, and configure resource consumption limits for the application.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50506 — 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-50506 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