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

GHSA-9v76-4qcc-frgh

HIGH

GHSA-9v76-4qcc-frgh is a high-severity (CVSS 7.5) CWE-835 vulnerability in Microsoft.AspNetCore.App.Runtime.win-arm. O3 Security confirms whether GHSA-9v76-4qcc-frgh is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

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

Also known asBIT-dotnet-2026-42899BIT-dotnet-sdk-2026-42899CVE-2026-42899
Published
May 18, 2026
Updated
Jun 9, 2026
Affected
36 pkgs
Patched
36 / 36
Exploits
None indexed
Exploitation data as of Aug 14, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • 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 GHSA-9v76-4qcc-frgh.

EPSS Exploitation Probability

via FIRST.org ↗
2.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs83th percentile — riskier than 83% of all scored CVEsHighest risk
0.00%1.05%2.10%3.15%0.0%2.4%2.4%2.4%Jun 26Aug 26Aug 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-9v76-4qcc-frgh plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 0 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

36 pkgs affected
.NETMicrosoft.AspNetCore.App.Runtime.win-arm.NETMicrosoft.AspNetCore.App.Runtime.win-arm64.NETMicrosoft.AspNetCore.App.Runtime.win-x64.NETMicrosoft.AspNetCore.App.Runtime.win-x86.NETMicrosoft.AspNetCore.App.Runtime.linux-arm.NETMicrosoft.AspNetCore.App.Runtime.linux-arm64.NETMicrosoft.AspNetCore.App.Runtime.linux-musl-arm.NETMicrosoft.AspNetCore.App.Runtime.linux-musl-arm64+28 more

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

Executive Summary:

Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 8.0, .NET 9.0, and .NET 10.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.

Loop with unreachable exit condition ('infinite loop') in ASP.NET Core allows an unauthorized attacker to deny service over a network.

Announcement

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

CVSS Details

  • Version: 3.1
  • Severity:
  • Score: 7.5
  • Vector: AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:U/RL:O/RC:C
  • Weakness: CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop')

Affected Platforms

  • Platforms: All
  • 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 10"></a>.NET 10

Package nameAffected versionPatched version
Microsoft.AspNetCore.App.Runtime.win-arm>= 10.0.0, <= 10.0.710.0.8
Microsoft.AspNetCore.App.Runtime.win-arm64>= 10.0.0, <= 10.0.710.0.8
Microsoft.AspNetCore.App.Runtime.win-x64>= 10.0.0, <= 10.0.710.0.8
Microsoft.AspNetCore.App.Runtime.win-x86>= 10.0.0, <= 10.0.710.0.8
Microsoft.AspNetCore.App.Runtime.linux-arm>= 10.0.0, <= 10.0.710.0.8
Microsoft.AspNetCore.App.Runtime.linux-arm64>= 10.0.0, <= 10.0.710.0.8
Microsoft.AspNetCore.App.Runtime.linux-musl-arm>= 10.0.0, <= 10.0.710.0.8
Microsoft.AspNetCore.App.Runtime.linux-musl-arm64>= 10.0.0, <= 10.0.710.0.8
Microsoft.AspNetCore.App.Runtime.linux-musl-x64>= 10.0.0, <= 10.0.710.0.8
Microsoft.AspNetCore.App.Runtime.linux-x64>= 10.0.0, <= 10.0.710.0.8
Microsoft.AspNetCore.App.Runtime.osx-arm64>= 10.0.0, <= 10.0.710.0.8
Microsoft.AspNetCore.App.Runtime.osx-x64>= 10.0.0, <= 10.0.710.0.8

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

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

Advisory FAQ

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

If using a package listed in affected packages, an application is 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 8.0, NET 9.0, or .NET 10.0, as appropriate. If developers have installed one or more .NET SDKs through Visual Studio, Visual Studio will prompt them to update Visual Studio, which will also update the application's .NET SDKs.
  2. If an application references the vulnerable package, update the package reference to the patched version. Developers can list the versions they have installed by running the dotnet --info command.

Once developers have installed the updated runtime or SDK, they should restart their apps for the update to take effect.

Additionally, if developers have 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 a potential security issue has been found 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

Questions about this issue can be submitted to 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. Questions can be submitted through 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-42899

Acknowledgements

hamayanhamayan Muhammad Abdul Rehman

Revisions

V1.0 (May 12, 2026): Advisory published.

Affected Packages

36 total 36 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetMicrosoft.AspNetCore.App.Runtime.win-arm8.0.0&&< 8.0.278.0.27
.NETNuGetMicrosoft.AspNetCore.App.Runtime.win-arm648.0.0&&< 8.0.278.0.27
.NETNuGetMicrosoft.AspNetCore.App.Runtime.win-x648.0.0&&< 8.0.278.0.27
.NETNuGetMicrosoft.AspNetCore.App.Runtime.win-x868.0.0&&< 8.0.278.0.27
.NETNuGetMicrosoft.AspNetCore.App.Runtime.linux-arm8.0.0&&< 8.0.278.0.27
.NETNuGetMicrosoft.AspNetCore.App.Runtime.linux-arm648.0.0&&< 8.0.278.0.27

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.App.Runtime.win-arm. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update Microsoft.AspNetCore.App.Runtime.win-arm to 8.0.27 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9v76-4qcc-frgh is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-9v76-4qcc-frgh is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-9v76-4qcc-frgh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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.

Frequently Asked Questions

## Executive Summary: Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 8.0, .NET 9.0, and .NET 10.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. Loop with unreachable exit condition ('infinite loop') in ASP.NET Core allows an unauthorized attacker to deny service over a network. ## Announcement Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/397 ## CVSS Details - **Version:** 3.1 - **Severity:** - **Score:** 7.5 - **V
O3 Security · Impact-Aware SCA

Is GHSA-9v76-4qcc-frgh in your dependencies?

O3 detects GHSA-9v76-4qcc-frgh across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.