CVE-2026-70159: ASP.NET Core Denial of Service Vulnerability

Published Oct 13, 2026
·
Updated

Executive summary

Microsoft is releasing this security advisory to provide information about a vulnerability in Microsoft.AspNetCore.SignalR.Common and Microsoft.AspNetCore.SignalR.Core. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.

SignalR stateful reconnect clients can indefinitely block broadcasts through MessageBuffer.ResendAsync backpressure and retain associated resources.

Announcement

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

CVSS Details

- Version: 3.1 - Severity: High - Score: 7.5 - Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

- Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling) Affected Platforms

- Platforms: Windows, Linux, macOS - Architectures: All

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

The vulnerability affects Microsoft .NET projects that use an affected package version listed below.

Package name | Affected version | Patched version ------------ | ---------------- | --------------- Microsoft.AspNetCore.SignalR.Common | >= 10.0.0, <= 10.0.12 | 10.0.13 Microsoft.AspNetCore.SignalR.Core | >= 1.0.0, <= 1.2.13 | 1.2.14 Microsoft.AspNetCore.SignalR.Common | >= 11.0.0-preview.5, <= 11.0.0-rc.1 | 11.0.0-rc.2 Microsoft.AspNetCore.SignalR.Common | >= 8.0.0, <= 8.0.31 | 8.0.32 Microsoft.AspNetCore.SignalR.Common | >= 9.0.0, <= 9.0.20 | 9.0.21

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

Acknowledgements

- nono - Vincent55 Yang (https://vincent55.tw/)

Revisions

V1.0 (10/13/2026): Advisory published.

Other sources

Allocation of resources without limits or throttling in ASP.NET Core allows an unauthorized attacker to deny service over a network.

— Microsoft

ASP.NET Core Denial of Service Vulnerability

— Microsoft

Affected Software

12 affected componentsFixes available
Microsoft Visual Studio 2022=17.14
17.14.42
Microsoft Microsoft.AspNetCore.SignalR.Core<1.2.14
1.2.14
Microsoft Microsoft.AspNetCore.SignalR.Common<9.0.21
9.0.21
Microsoft Microsoft.AspNetCore.SignalR.Common<8.0.32
8.0.32
Microsoft Microsoft.AspNetCore.SignalR.Common<10.0.13
10.0.13
Microsoft Microsoft.AspNetCore.SignalR.Common<11.0.0-rc.2
11.0.0-rc.2
Microsoft Visual Studio 2026=18.10
18.10.4
nuget/Microsoft.AspNetCore.SignalR.Common>=9.0.0<=9.0.20
9.0.21
nuget/Microsoft.AspNetCore.SignalR.Common>=8.0.0<=8.0.31
8.0.32
nuget/Microsoft.AspNetCore.SignalR.Common>=11.0.0-preview.5<=11.0.0-rc.1
11.0.0-rc.2
nuget/Microsoft.AspNetCore.SignalR.Core>=1.0.0<=1.2.13
1.2.14
nuget/Microsoft.AspNetCore.SignalR.Common>=10.0.0<=10.0.12
10.0.13

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 17.14.42
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.2.14
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 9.0.21
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 8.0.32
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.13
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 11.0.0-rc.2
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 18.10.4
  8. Upgrade

    Upgrade nuget/Microsoft.AspNetCore.SignalR.Common to a version that resolves this vulnerability.

    Fixed in 9.0.21
  9. Upgrade

    Upgrade nuget/Microsoft.AspNetCore.SignalR.Common to a version that resolves this vulnerability.

    Fixed in 8.0.32
  10. Upgrade

    Upgrade nuget/Microsoft.AspNetCore.SignalR.Common to a version that resolves this vulnerability.

    Fixed in 11.0.0-rc.2
  11. Upgrade

    Upgrade nuget/Microsoft.AspNetCore.SignalR.Core to a version that resolves this vulnerability.

    Fixed in 1.2.14
  12. Upgrade

    Upgrade nuget/Microsoft.AspNetCore.SignalR.Common to a version that resolves this vulnerability.

    Fixed in 10.0.13
  13. Upgrade

    Upgrade Microsoft.AspNetCore.SignalR.Common to a version that resolves this vulnerability.

    Fixed in 10.0.13
  14. Upgrade

    Upgrade Microsoft.AspNetCore.SignalR.Common to a version that resolves this vulnerability.

    Fixed in 11.0.0-rc.2
  15. Upgrade

    Upgrade Microsoft.AspNetCore.SignalR.Common to a version that resolves this vulnerability.

    Fixed in 8.0.32
  16. Upgrade

    Upgrade Microsoft.AspNetCore.SignalR.Common to a version that resolves this vulnerability.

    Fixed in 9.0.21
  17. Upgrade

    Upgrade Microsoft.AspNetCore.SignalR.Core to a version that resolves this vulnerability.

    Fixed in 1.2.14
  18. Operational

    Recompile and redeploy self-contained applications targeting impacted versions.

  19. Operational

    Restart applications after installing the updated runtime or SDK.

Event History

Oct 13, 2026
CVE Published
via Microsoft·02:00 PM
Data Sourced
via Microsoft·02:00 PM
DescriptionSeverityWeaknessAffected Software
CVE Published
via MITRE·07:00 PM
Data Sourced
via MITRE·07:00 PM
DescriptionSeverity
Advisory Published
via GitHub·07:41 PM
Data Sourced
via GitHub·07:41 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Which applications are exposed?

Microsoft .NET projects that use affected versions of Microsoft.AspNetCore.SignalR.Common or Microsoft.AspNetCore.SignalR.Core are affected. The issue applies on Windows, Linux, and macOS across all architectures.

2

What does an attacker need to exploit this issue?

The CVSS vector indicates exploitation is network-accessible, has low attack complexity, and requires neither privileges nor user interaction. The impact is denial of service through blocked SignalR broadcasts and retained resources associated with stateful reconnect clients.

3

What should developers do to remediate the issue?

Update affected applications to patched versions of the affected SignalR packages. The advisory specifically identifies Microsoft.AspNetCore.SignalR.Common and Microsoft.AspNetCore.SignalR.Core as the packages requiring attention.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203