Allocation of Resources Without Limits or Throttling Affecting microsoft.aspnetcore.odata package, versions [,9.5.0)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Allocation of Resources Without Limits or Throttling vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-DOTNET-MICROSOFTASPNETCOREODATA-19666383
- published10 Sept 2026
- disclosed14 Jul 2026
- creditUnknown
Introduced: 14 Jul 2026
CVE-2026-50506 (opens in a new tab)How to fix?
Upgrade Microsoft.AspNetCore.OData to version 9.5.0 or higher.
Overview
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in the ODataBatchHandler and its reader and writer settings, which override the parser's conservative 1 MB MaxReceivedMessageSize default with Int64.MaxValue, removing the size limit on request bodies. An attacker can exhaust server memory by sending an oversized OData request body to a POST, PUT, PATCH, or $batch endpoint. This requires OData endpoints reachable by untrusted clients, which is the standard deployment.
Workaround
This vulnerability can be avoided by enforcing a request body size limit at the host or reverse proxy layer, such as Kestrel's MaxRequestBodySize or IIS maxAllowedContentLength, so oversized payloads are rejected before OData reads them.