CVE-2026-85790: Microsoft QUIC Information Disclosure Vulnerability
Executive summary
Microsoft is releasing this security advisory to provide information about a vulnerability in Microsoft.Native.Quic.MsQuic.Schannel. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
Various vulnerabilities in MsQuic are addressed by an updated native-binary dependency update.
Announcement
Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/470
CVSS Details
- Version: 3.1 - Severity: Moderate - Score: 5.9 - Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- Weakness: CWE-416 (Use After Free) Affected Platforms
- Platforms: Windows - 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.Native.Quic.MsQuic.Schannel | >= 1.9.0, <= 2.6.1 | 2.6.2
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-85790
Acknowledgements
- reinusKR
Revisions
V1.0 (10/13/2026): Advisory published.
Other sources
Microsoft QUIC Information Disclosure Vulnerability
— Microsoft
Use after free in Microsoft QUIC allows an unauthorized attacker to disclose information over a network.
— Microsoft
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.22631.7652Patch KB5126653 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.26200.9711Patch KB5127648 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.28000.3231Patch KB5127646 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2.6.2 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.26100.9711Patch KB5127648 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.26100.33650Patch KB5126646 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.20348.5761Patch KB5126655 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 17.14.42 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.26300.9711Patch KB5127648 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 18.10.4 - Upgrade
Upgrade
nuget/Microsoft.Native.Quic.MsQuic.Schannelto a version that resolves this vulnerability.Fixed in 2.6.2 - Upgrade
Upgrade
Microsoft.Native.Quic.MsQuic.Schannelto a version that resolves this vulnerability.Fixed in 2.6.2 - Operational
If self-contained applications target an affected version, recompile and redeploy them.
- Operational
Restart applications after installing the updated runtime or SDK.
Event History
Frequently Asked Questions
Which applications should be prioritized for remediation?
Prioritize Windows-hosted .NET projects that depend on Microsoft.Native.Quic.MsQuic.Schannel at versions 1.9.0 through 2.6.1. The advisory identifies all Windows architectures as affected.
What does an attacker need to exploit this issue?
The CVSS vector indicates that exploitation is network-accessible and requires no privileges or user interaction. It also has high attack complexity, so additional conditions are required for successful exploitation.
How can I determine whether a project is affected?
Inspect the project's resolved NuGet dependencies for Microsoft.Native.Quic.MsQuic.Schannel. A resolved version from 1.9.0 through 2.6.1 is affected.
What is the remediation?
Update Microsoft.Native.Quic.MsQuic.Schannel to version 2.6.2. The advisory describes the fix as an updated native-binary dependency update.