CVE-2026-118750

Allocation of resources without limits or throttling in ASP.NET Core allows an unauthorized attacker to deny service over a network.

Allocation of resources without limits or throttling in ASP.NET Core allows an unauthorized attacker to deny service over a network.

Executive summary

Microsoft is releasing this security advisory to provide information about a vulnerability in ASP.NET Core. This advisory provides guidance on updating affected applications and components.

FileBufferingReadStream buffer allocation can allow unauthenticated multipart-form requests to exhaust memory.

Announcement

Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/512

CVSS Details

• Version: 3.1
• Severity: High
• Score: 7.5 (base score)
• Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:U/RL:O/RC:C
• Weakness: CWE-770

Affected Platforms

• Platforms: Any supported OS
• Architectures: All

<a name="affected-packages"></a>Affected Packages

The table lists the affected package range and the fixed NuGet version.

ASP.NET Core 2.3 - standalone packages

Package | Affected version | Patched version --- | --- | --- Microsoft.AspNetCore.WebUtilities | >= 2.3.0, <= 2.3.13 | 2.3.14

Advisory FAQ

<a name="how-affected"></a>How do I know if I am affected?

Check the application's Microsoft.AspNetCore.WebUtilities package reference against the affected range above, including transitive dependencies brought in by Microsoft.AspNetCore.Http. Use dotnet list <PROJECT> package --include-transitive to inspect resolved dependencies.

<a name="how-fix"></a>How do I fix the issue?

Update each applicable package reference to its patched version listed above, then rebuild and redeploy the application. Updating only the installed runtime does not update an application's standalone package references.

Applications referencing Microsoft.AspNetCore.Http must resolve Microsoft.AspNetCore.WebUtilities to version 2.3.14 or later. Add or update a direct WebUtilities reference if necessary to override an older transitive dependency.

Other Information

Reporting Security Issues

If you have found a potential security issue in a supported version of .NET, please report it to the Microsoft Security Response Center (MSRC) via the MSRC Researcher Portal. Further information can be found in the MSRC Report an Issue FAQ.

Security reports made through MSRC may qualify for the Microsoft .NET Bounty. Details of the Microsoft .NET Bounty Program including terms and conditions are at https://aka.ms/corebounty.

Support

You can ask questions about this issue on GitHub in the .NET GitHub organization. The main repos are located at https://github.com/dotnet/runtime. The Announcements repo (https://github.com/dotnet/Announcements) will contain this bulletin as an issue and will include a link to a discussion issue. You can ask questions in the linked discussion issue.

Disclaimer

The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.

External Links

CVE-2026-118750

Acknowledgements

• NavSec4

Revisions

V1.0 (November 10, 2026): Advisory published.

Allocation of resources without limits or throttling in ASP.NET Core allows an unauthorized attacker to deny service over a network.

Executive summary

Microsoft is releasing this security advisory to provide information about a vulnerability in ASP.NET Core. This advisory provides guidance on updating affected applications and components.

FileBufferingReadStream buffer allocation can allow unauthenticated multipart-form requests to exhaust memory.

Announcement

Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/512

CVSS Details

• Version: 3.1
• Severity: High
• Score: 7.5 (base score)
• Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:U/RL:O/RC:C
• Weakness: CWE-770

Affected Platforms

• Platforms: Any supported OS
• Architectures: All

<a name="affected-packages"></a>Affected Packages

The table lists the affected package range and the fixed NuGet version.

ASP.NET Core 2.3 - standalone packages

Package | Affected version | Patched version --- | --- | --- Microsoft.AspNetCore.WebUtilities | >= 2.3.0, <= 2.3.13 | 2.3.14

Advisory FAQ

<a name="how-affected"></a>How do I know if I am affected?

Check the application's Microsoft.AspNetCore.WebUtilities package reference against the affected range above, including transitive dependencies brought in by Microsoft.AspNetCore.Http. Use dotnet list <PROJECT> package --include-transitive to inspect resolved dependencies.

<a name="how-fix"></a>How do I fix the issue?

Update each applicable package reference to its patched version listed above, then rebuild and redeploy the application. Updating only the installed runtime does not update an application's standalone package references.

Applications referencing Microsoft.AspNetCore.Http must resolve Microsoft.AspNetCore.WebUtilities to version 2.3.14 or later. Add or update a direct WebUtilities reference if necessary to override an older transitive dependency.

Other Information

Reporting Security Issues

If you have found a potential security issue in a supported version of .NET, please report it to the Microsoft Security Response Center (MSRC) via the MSRC Researcher Portal. Further information can be found in the MSRC Report an Issue FAQ.

Security reports made through MSRC may qualify for the Microsoft .NET Bounty. Details of the Microsoft .NET Bounty Program including terms and conditions are at https://aka.ms/corebounty.

Support

You can ask questions about this issue on GitHub in the .NET GitHub organization. The main repos are located at https://github.com/dotnet/runtime. The Announcements repo (https://github.com/dotnet/Announcements) will contain this bulletin as an issue and will include a link to a discussion issue. You can ask questions in the linked discussion issue.

Disclaimer

The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.

External Links

CVE-2026-118750

Acknowledgements

• NavSec4

Revisions

V1.0 (November 10, 2026): Advisory published.