Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
.NET
.NET NuGet
Not in CISA KEV
MEDIUM severity

CVE-2026-69304 — Microsoft.AspNetCore.Serv…

MEDIUM

CVE-2026-69304 is a medium-severity (CVSS 5.9) CWE-409 vulnerability in Microsoft.AspNetCore.Server.IISIntegration. A fix is available for Microsoft.AspNetCore.Server.IISIntegration — see the affected versions and patch details below.

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

Also known asBIT-aspnet-core-2026-69304BIT-dotnet-2026-69304BIT-dotnet-sdk-2026-69304GHSA-8cp2-47hg-mfgh
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-69304.

EPSS Exploitation Probability

via FIRST.org ↗
0.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs59th percentile — riskier than 59% of all scored CVEsHighest risk
0.38%0.71%1.04%1.38%0.9%0.9%Oct 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2026-69304 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 395,249 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

4 pkgs affected
.NETMicrosoft.AspNetCore.Server.IISIntegration.NETMicrosoft.AspNetCore.Server.IISIntegration.NETMicrosoft.AspNetCore.Server.IISIntegration.NETMicrosoft.AspNetCore.Server.IISIntegration

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

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 https://github.com/dotnet/announcements/issues/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

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

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

<a name=".NET 11 RC1"></a>.NET 11 RC1

Package nameAffected versionPatched version
Microsoft.AspNetCore.Server.IISIntegration>= 11.0.0-preview.1, < 11.0.0-rc.111.0.0-rc.1

<a name=".NET 10"></a>.NET 10

Package nameAffected versionPatched version
Microsoft.AspNetCore.Server.IISIntegration>= 10.0.0, <= 10.0.1110.0.12

<a name=".NET 9"></a>.NET 9

Package nameAffected versionPatched version
Microsoft.AspNetCore.Server.IISIntegration>= 9.0.0, <= 9.0.199.0.20

<a name=".NET 8"></a>.NET 8

Package nameAffected versionPatched version
Microsoft.AspNetCore.Server.IISIntegration>= 8.0.0, <= 8.0.308.0.31

Advisory FAQ

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

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

<a name="how-fix"></a>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.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetMicrosoft.AspNetCore.Server.IISIntegration≥ 11.0.0-preview.1&&< 11.0.0-rc.111.0.0-rc.1dotnet add package Microsoft.AspNetCore.Server.IISIntegration --version 11.0.0-rc.1
.NETNuGetMicrosoft.AspNetCore.Server.IISIntegration≥ 8.0.0&&< 8.0.318.0.31dotnet add package Microsoft.AspNetCore.Server.IISIntegration --version 8.0.31
.NETNuGetMicrosoft.AspNetCore.Server.IISIntegration≥ 9.0.0&&< 9.0.209.0.20dotnet add package Microsoft.AspNetCore.Server.IISIntegration --version 9.0.20
.NETNuGetMicrosoft.AspNetCore.Server.IISIntegration≥ 10.0.0&&< 10.0.1210.0.12dotnet add package Microsoft.AspNetCore.Server.IISIntegration --version 10.0.12

Affected Products

4 products · 10 configurations
Application
.netmicrosoft
≥ 10.0.0 && < 10.0.12
range
Application
asp.net coremicrosoft
≥ 10.0.0 && < 10.0.9
1 version
11.0
Application
visual studio 2022microsoft
≥ 17.14.0 && < 17.14.40
range
Application
visual studio 2026microsoft
≥ 18.9.0 && < 18.9.3
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Microsoft.AspNetCore.Server.IISIntegration, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update Microsoft.AspNetCore.Server.IISIntegration to 11.0.0-rc.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-69304 is resolved across your whole dependency graph.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate
ProductFixed inAdvisory
Red Hat Hardened Imagesdotnet10-0-main-10.0.112-1.hum1RHSA-2026:66863
Red Hat Hardened Imagesdotnet9-0-main-9.0.119-2.1.hum1RHSA-2026:74947
Red Hat Hardened Imagesdotnet8-0-main-8.0.130-0.2.hum1RHSA-2026:74950

Frequently Asked Questions

# 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 fo
O3 Security · Impact-Aware SCA

Is CVE-2026-69304 in your dependencies?

Find it across NuGet, including transitive dependencies.

CVE-2026-69304: DoS — Fixed in 11.0.0-rc.1