Skip to content

Microsoft Security Advisory CVE-2026-69304 – ASP.NET Core Denial of Service Vulnerability

Moderate severity GitHub Reviewed Published Sep 8, 2026 in dotnet/aspnetcore • Updated Sep 9, 2026

Package

nuget Microsoft.AspNetCore.Server.IISIntegration (NuGet)

Affected versions

>= 11.0.0-preview.1, < 11.0.0-rc.1
>= 8.0.0, <= 8.0.30
>= 9.0.0, <= 9.0.19
>= 10.0.0, <= 10.0.11

Patched versions

11.0.0-rc.1
8.0.31
9.0.20
10.0.12

Description

Microsoft Security Advisory CVE-2026-69304 – ASP.NET Core Denial of Service Vulnerability

Executive summary

Microsoft is releasing this security advisory to provide information about a vulnerability in ASP.NET Core IIS out-of-process hosting and request decompression. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.

The IIS Middleware for ASP.NET Core did not properly constrain decompression of certain types of request, leading to excess memory consumption and a Denial of Service.

Announcement

Announcement for this issue can be found at dotnet/announcements#443

CVSS Details

  • Version: 3.1
  • Severity: Medium
  • Score: 5.9
  • Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
  • Weakness: CWE-409 (Improper Handling of Highly Compressed Data (Data Amplification))

Affected Platforms

  • Platforms: Windows / IIS out-of-process
  • Architectures: All

Affected Packages

The vulnerability affects any Microsoft .NET project if it uses any of affected package versions listed below

.NET 11 RC1

Package name Affected version Patched version
Microsoft.AspNetCore.Server.IISIntegration >= 11.0.0-preview.1, < 11.0.0-rc.1 11.0.0-rc.1

.NET 10

Package name Affected version Patched version
Microsoft.AspNetCore.Server.IISIntegration >= 10.0.0, <= 10.0.11 10.0.12

.NET 9

Package name Affected version Patched version
Microsoft.AspNetCore.Server.IISIntegration >= 9.0.0, <= 9.0.19 9.0.20

.NET 8

Package name Affected version Patched version
Microsoft.AspNetCore.Server.IISIntegration >= 8.0.0, <= 8.0.30 8.0.31

Advisory FAQ

How do I know if I am affected?

If using a package listed in affected packages, you're exposed to the vulnerability.

How do I fix the issue?

  1. To fix the issue please install the latest version of .NET. If you have installed one or more .NET SDKs through Visual Studio, Visual Studio will prompt you to update Visual Studio, which will also update your .NET SDKs.
  2. If your application references the vulnerable package, update the package reference to the patched version. You can list the versions you have installed by running the dotnet --info command.

Once you have installed the updated runtime or SDK, restart your apps for the update to take effect.

Additionally, if you've deployed self-contained applications targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed.

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-69304

Acknowledgements

محمد السيد عثمان محمود القصاص

Anonymous

Revisions

V1.0 (09/08/2026): Advisory published.

References

@bribrothers bribrothers published to dotnet/aspnetcore Sep 8, 2026
Published to the GitHub Advisory Database Sep 9, 2026
Reviewed Sep 9, 2026
Last updated Sep 9, 2026

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(53rd percentile)

Weaknesses

Improper Handling of Highly Compressed Data (Data Amplification)

The product does not handle or incorrectly handles a compressed input with a very high compression ratio that produces a large output. Learn more on MITRE.

CVE ID

CVE-2026-69304

GHSA ID

GHSA-8cp2-47hg-mfgh

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.