Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
.NET NuGet

GHSA-4vgm-c2wm-63mw

HIGH

GHSA-4vgm-c2wm-63mw is a high-severity (CVSS 7.5) CWE-770 vulnerability in Microsoft.AspNetCore.App.Runtime.linux-arm. O3 Security confirms whether GHSA-4vgm-c2wm-63mw is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

.NET Denial of Service Vulnerability

Also known asBIT-aspnet-core-2026-26130CVE-2026-26130
Published
Mar 11, 2026
Updated
Apr 6, 2026
Affected
36 pkgs
Patched
36 / 36
Exploits
None indexed

Blast Radius

36 pkgs affected
.NETMicrosoft.AspNetCore.App.Runtime.linux-arm.NETMicrosoft.AspNetCore.App.Runtime.linux-arm.NETMicrosoft.AspNetCore.App.Runtime.linux-arm.NETMicrosoft.AspNetCore.App.Runtime.linux-arm64.NETMicrosoft.AspNetCore.App.Runtime.linux-arm64.NETMicrosoft.AspNetCore.App.Runtime.linux-arm64.NETMicrosoft.AspNetCore.App.Runtime.linux-musl-arm.NETMicrosoft.AspNetCore.App.Runtime.linux-musl-arm+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

Microsoft Security Advisory CVE-2026-26130 – .NET Denial of Service Vulnerability

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.

A denial of service vulnerability exists in ASP.NET Core due to uncontrolled resource consumption. A specially crafted message to a SignalR server can exhaust an internal buffer and cause a Denial of Service.

Announcement

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

CVSS Details

  • Version: 3.1
  • Score: 7.5
  • 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
  • Severity: High
  • Weakness: CWE-770 (Uncontrolled Resource Consumption)

Affected Platforms

  • Platforms: All
  • Architectures: All

Affected Products

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

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

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

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

Advisory FAQ

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

If using an affected package listed in affected products or 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 8.0, NET 9.0, or .NET 10.0, as appropriate. 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-26130

Acknowledgements

Bartłomiej Dach

Revisions

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

Affected Packages

36 total 36 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetMicrosoft.AspNetCore.App.Runtime.linux-arm8.0.0&&< 8.0.258.0.25
.NETNuGetMicrosoft.AspNetCore.App.Runtime.linux-arm9.0.0&&< 9.0.149.0.14
.NETNuGetMicrosoft.AspNetCore.App.Runtime.linux-arm10.0.0&&< 10.0.410.0.4
.NETNuGetMicrosoft.AspNetCore.App.Runtime.linux-arm648.0.0&&< 8.0.258.0.25
.NETNuGetMicrosoft.AspNetCore.App.Runtime.linux-arm649.0.0&&< 9.0.149.0.14
.NETNuGetMicrosoft.AspNetCore.App.Runtime.linux-arm6410.0.0&&< 10.0.410.0.4

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.linux-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.linux-arm to 8.0.25 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4vgm-c2wm-63mw 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-4vgm-c2wm-63mw 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-4vgm-c2wm-63mw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

# Microsoft Security Advisory CVE-2026-26130 – .NET Denial of Service Vulnerability ## 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. A denial of service vulnerability exists in ASP.NET Core due to uncontrolled resource consumption. A specially crafted message to a SignalR server can exhaust an internal buffer and cause a Denial of Service. ## Announcement Announcement f
O3 Security · Impact-Aware SCA

Is GHSA-4vgm-c2wm-63mw in your dependencies?

O3 detects GHSA-4vgm-c2wm-63mw across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.