CVE-2026-114146 — Microsoft.AspNetCore.Http…

Executive summary

Microsoft is releasing this security advisory to provide information about a vulnerability in ASP.NET Core. This advisory provides guidance on updating affected applications and components.

SignalR connections are not consistently bound to the identity negotiated at connection establishment, allowing injected messages to execute Hub invocations as the victim.

Announcement

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

CVSS Details

• Version: 3.1
• Severity: Critical
• Score: 9.0 (base score)
• Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H/E:U/RL:O/RC:C
• Weakness: CWE-863

Affected Platforms

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

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

The tables list affected version ranges and fixed package versions. Runtime and standalone deliveries are listed separately.

ASP.NET Core 2.3 - standalone packages

.NET 8.0 - affected runtime packages

.NET 9.0 - affected runtime packages

.NET 10.0 - affected runtime packages

.NET 11.0 - affected runtime packages

Advisory FAQ

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

Check the deployed runtime and application package versions against the affected ranges above. Self-contained applications include their own runtime; updating a machine-wide runtime does not replace it.

<a name="how-fix"></a>How do I fix the issue?

Install the applicable runtime or update each independently referenced package to the fixed version above. After updating standalone packages, rebuild and redeploy affected applications, including framework-dependent applications; restarting alone does not replace app-local packages. Restart applications. Rebuild and redeploy self-contained applications; updating a machine-wide runtime does not replace their embedded runtime. An SDK update alone does not update an application's standalone package references.

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

Acknowledgements

• Mika Vehns with MIVE GmbH
• Lucas Gabriel
• hsuan0223x
• Mariusz Maik
• Pocas (Jeongwon Jo)
• Grace Chapel
• Jacob Keith with Keith Systems
• Weeraphat Srisutham
• Kevin Gosse
• Artur Stetsko
• Yudai Shibata
• 71C4
• Attila Csatadi of ZeroDayBugs.com
• Vu Van Tien ( @n0_Be3r )

Revisions

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