CVE-2026-69304: ASP.NET Core Denial of Service Vulnerability
Noroxi assessment
Priority: Monitor (action score 23/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.85% (FIRST EPSS); higher than 58.3% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: .NET 10.0 runtime installed on Windows 10.0.12; .NET 8.0 runtime installed on Windows 8.0.31; .NET 9.0 runtime installed on Windows 9.0.20.
Low priority for now. Upgrade to .NET 10.0 runtime installed on Windows 10.0.12; .NET 8.0 runtime installed on Windows 8.0.31; .NET 9.0 runtime installed on Windows 9.0.20 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Improper handling of highly compressed data (data amplification) in ASP.NET Core allows an unauthorized attacker to deny service over a network.
- Published
- Sep 8, 2026
- Updated
- Oct 31, 2026
- EPSS
- 0.8% · 58th percentile
- CWE
- CWE-409
Report tools
Action score
23
Monitor
Low priority for now.
- CVSS
- 23 / 40 · 5.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.8%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.9
- CNA · microsoft
- 5.9
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| microsoft | asp.net core | cpe:2.3:a:microsoft:asp.net_core |
| microsoft | visual studio 2022 | cpe:2.3:a:microsoft:visual_studio_2022 |
| microsoft | visual studio 2026 | cpe:2.3:a:microsoft:visual_studio_2026 |
| microsoft | .net | cpe:2.3:a:microsoft:.net |
| microsoft | windows | cpe:2.3:o:microsoft:windows |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- microsoft .net10.0.0 and later · before 10.0.12
- microsoft .net9.0.0 and later · before 9.0.20
- microsoft .net8.0.0 and later · before 8.0.31
- microsoft asp.net coreafter 11.0.0
- microsoft asp.net core8.0.0 and later · before 8.0.28
- microsoft asp.net core9.0.0 and later · before 9.0.17
- microsoft asp.net core10.0.0 and later · before 10.0.9
- microsoft asp.net core11.0
- microsoft visual studio 202217.14.0 and later · before 17.14.40
- microsoft visual studio 202618.9.0 and later · before 18.9.3
Versions reported by the vendor
Affected version ranges reported by the assigning authority (microsoft). Independent of NVD's CPE analysis and usually ahead of it.
Microsoft .NET 10.0 runtime
- 10.0.0 and later · before 10.0.12affected
Microsoft .NET 8.0 runtime
- 8.0.0 and later · before 8.0.31affected
Microsoft .NET 9.0 runtime
- 9.0.0 and later · before 9.0.20affected
Microsoft ASP.NET Core 10.0
- 10.0 and later · before 10.0.12affected
Microsoft ASP.NET Core 11.0
- 11.0 and later · before 11.0 RC1affected
Microsoft ASP.NET Core 8.0
- 8.0 and later · before 8.0.31affected
Microsoft ASP.NET Core 9.0
- 9.0 and later · before 9.0.20affected
Microsoft Microsoft Visual Studio 2022 version 17.14
- 17.14.0 and later · before 17.14.40affected
Microsoft Microsoft Visual Studio 2026 version 18.9
- 18.9.0 and later · before 18.9.3affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| NuGet | Microsoft.AspNetCore.Server.IISIntegration | from 10.0.0 · before 10.0.12 | 10.0.12 |
| NuGet | Microsoft.AspNetCore.Server.IISIntegration | from 11.0.0-preview.1 · before 11.0.0-rc.1 | 11.0.0-rc.1 |
| NuGet | Microsoft.AspNetCore.Server.IISIntegration | from 8.0.0 · before 8.0.31 | 8.0.31 |
| NuGet | Microsoft.AspNetCore.Server.IISIntegration | from 9.0.0 · before 9.0.20 | 9.0.20 |
| Red Hat:hummingbird:1 | aspnetcore-runtime-8.0 | before 0:8.0.30-0.2.hum1 | 0:8.0.30-0.2.hum1 |
| Red Hat:hummingbird:1 | aspnetcore-runtime-9.0 | before 0:9.0.18-2.1.hum1 | 0:9.0.18-2.1.hum1 |
| Red Hat:hummingbird:1 | aspnetcore-runtime-dbg-8.0 | before 0:8.0.30-0.2.hum1 | 0:8.0.30-0.2.hum1 |
| Red Hat:hummingbird:1 | aspnetcore-runtime-dbg-9.0 | before 0:9.0.18-2.1.hum1 | 0:9.0.18-2.1.hum1 |
| Red Hat:hummingbird:1 | aspnetcore-targeting-pack-8.0 | before 0:8.0.30-0.2.hum1 | 0:8.0.30-0.2.hum1 |
| Red Hat:hummingbird:1 | aspnetcore-targeting-pack-9.0 | before 0:9.0.18-2.1.hum1 | 0:9.0.18-2.1.hum1 |
| Red Hat:hummingbird:1 | dotnet-apphost-pack-8.0 | before 0:8.0.30-0.2.hum1 | 0:8.0.30-0.2.hum1 |
| Red Hat:hummingbird:1 | dotnet-apphost-pack-9.0 | before 0:9.0.18-2.1.hum1 | 0:9.0.18-2.1.hum1 |
| Red Hat:hummingbird:1 | dotnet-hostfxr-8.0 | before 0:8.0.30-0.2.hum1 | 0:8.0.30-0.2.hum1 |
| Red Hat:hummingbird:1 | dotnet-hostfxr-9.0 | before 0:9.0.18-2.1.hum1 | 0:9.0.18-2.1.hum1 |
| Red Hat:hummingbird:1 | dotnet-runtime-8.0 | before 0:8.0.30-0.2.hum1 | 0:8.0.30-0.2.hum1 |
| Red Hat:hummingbird:1 | dotnet-runtime-9.0 | before 0:9.0.18-2.1.hum1 | 0:9.0.18-2.1.hum1 |
| Red Hat:hummingbird:1 | dotnet-runtime-dbg-8.0 | before 0:8.0.30-0.2.hum1 | 0:8.0.30-0.2.hum1 |
| Red Hat:hummingbird:1 | dotnet-runtime-dbg-9.0 | before 0:9.0.18-2.1.hum1 | 0:9.0.18-2.1.hum1 |
| Red Hat:hummingbird:1 | dotnet-sdk-10.0 | before 0:10.0.112-1.hum1 | 0:10.0.112-1.hum1 |
| Red Hat:hummingbird:1 | dotnet-sdk-10.0-source-built-artifacts | before 0:10.0.112-1.hum1 | 0:10.0.112-1.hum1 |
| Red Hat:hummingbird:1 | dotnet-sdk-8.0 | before 0:8.0.130-0.2.hum1 | 0:8.0.130-0.2.hum1 |
| Red Hat:hummingbird:1 | dotnet-sdk-8.0-source-built-artifacts | before 0:8.0.130-0.2.hum1 | 0:8.0.130-0.2.hum1 |
| Red Hat:hummingbird:1 | dotnet-sdk-9.0 | before 0:9.0.119-2.1.hum1 | 0:9.0.119-2.1.hum1 |
| Red Hat:hummingbird:1 | dotnet-sdk-9.0-source-built-artifacts | before 0:9.0.119-2.1.hum1 | 0:9.0.119-2.1.hum1 |
+14
Same product
microsoft: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-55315ASP.NET Security Feature Bypass Vulnerability59Plan
- CVE-2020-0603A remote code execution vulnerability exists in ASP.NET Core software when the software fails to handle objects in memory.An attacker who su41Plan
- CVE-2026-40372ASP.NET Core Elevation of Privilege Vulnerability39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-26130Mar 10, 2026 · ASP.NET Core Denial of Service Vulnerability31Monitor
- ← EarlierCVE-2026-45591Jun 9, 2026 · ASP.NET Core Denial of Service Vulnerability31Monitor
- Later →CVE-2026-88092Oct 13, 2026 · ASP.NET Core Tampering Vulnerability37Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| .NET 10.0 runtime installed on Windows | 10.0.12 · KB5126106 | Microsoft (MSRC) |
| .NET 8.0 runtime installed on Windows | 8.0.31 · KB5126104 | Microsoft (MSRC) |
| .NET 9.0 runtime installed on Windows | 9.0.20 · KB5126105 | Microsoft (MSRC) |
| ASP.NET Core 10.0 | 10.0.12 · KB5126106 | Microsoft (MSRC) |
| ASP.NET Core 11.0 | 11.0 RC1 | Microsoft (MSRC) |
| ASP.NET Core 8.0 | 8.0.31 · KB5126104 | Microsoft (MSRC) |
| ASP.NET Core 9.0 | 9.0.20 · KB5126105 | Microsoft (MSRC) |
| Microsoft Visual Studio 2022 version 17.14 | 17.14.40 · Release Notes | Microsoft (MSRC) |
| Microsoft Visual Studio 2026 version 18.9 | 18.9.3 · Release Notes | Microsoft (MSRC) |
| NuGet:Microsoft.AspNetCore.Server.IISIntegration | 10.0.12 | Package registry (OSV) |
| NuGet:Microsoft.AspNetCore.Server.IISIntegration | 11.0.0-rc.1 | Package registry (OSV) |
| NuGet:Microsoft.AspNetCore.Server.IISIntegration | 8.0.31 | Package registry (OSV) |
| NuGet:Microsoft.AspNetCore.Server.IISIntegration | 9.0.20 | Package registry (OSV) |
| red hat:aspnetcore-runtime-9.0 | 0:9.0.18-2.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:aspnetcore-runtime-dbg-9.0 | 0:9.0.18-2.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:aspnetcore-targeting-pack-9.0 | 0:9.0.18-2.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:dotnet-apphost-pack-9.0 | 0:9.0.18-2.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:dotnet-hostfxr-9.0 | 0:9.0.18-2.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:dotnet-runtime-9.0 | 0:9.0.18-2.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:dotnet-sdk-10.0 | 0:10.0.112-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:dotnet-sdk-10.0-source-built-artifacts | 0:10.0.112-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:dotnet-sdk-aot-10.0 | 0:10.0.112-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:dotnet-sdk-dbg-10.0 | 0:10.0.112-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:dotnet-templates-10.0 | 0:10.0.112-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:dotnet10.0 | 0:10.0.112-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-409 · Improper Handling of Highly Compressed Data (Data Amplification)CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.