CVE-2026-105016: Microsoft QUIC Remote Code Execution Vulnerability

Published Oct 13, 2026
·
Updated

Executive summary

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

A crafted IPv6 QUIC packet can reach the Microsoft QUIC HTTP/3 path without authentication or user interaction and trigger remote code execution.

Announcement

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

CVSS Details

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

- Weakness: CWE-122 (Heap-based Buffer Overflow) 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 | >= 2.5.11-ci.156755675, <= 2.5.11-ci.156755675 | 2.5.11-ci.159417053

Advisory FAQ

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

If your application uses a package version listed in affected packages, it is exposed to the vulnerability.

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

1. Install the latest servicing update for your supported .NET release. 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 directly references Microsoft.Native.Quic.MsQuic.Schannel, update the package reference to version 2.5.11-ci.159417053 or later. You can list the .NET versions installed on your system by running the dotnet --info command.

Once you have installed the updated runtime or SDK, restart your applications for the update to take effect.

Additionally, if you 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 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 repositories are located at https://github.com/dotnet/runtime. The Announcements repository (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-105016

Acknowledgements

pwn2addr

Revisions

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

Other sources

Heap-based buffer overflow in Microsoft QUIC allows an unauthorized attacker to execute code over a network.

— Microsoft

Microsoft QUIC Remote Code Execution Vulnerability

— Microsoft

Affected Software

22 affected componentsFixes available
Microsoft Microsoft QUIC
Microsoft Windows 11=26H2
10.0.26300.9711
Microsoft Windows 11=25H2
10.0.26200.9711
Microsoft Windows 11=24H2
10.0.26100.9711
Microsoft Windows Server 2025<10.0.26100.33650
10.0.26100.33650
Microsoft .NET 11.0 installed on Windows<11.0.0-rc.2.26504.105
11.0.0-rc.2.26504.105
Microsoft .NET 9.0 installed on Windows<9.0.21
9.0.21
Microsoft Windows Server 2025<10.0.26100.33650
10.0.26100.33650
Microsoft Windows 11=26H1
10.0.28000.3231
Microsoft Visual Studio 2022=17.14
17.14.42
Microsoft Windows 11=26H2
10.0.26300.9711
Microsoft .NET 10.0 installed on Windows<10.0.14
10.0.14
Microsoft .NET 8.0 installed on Windows<8.0.32
8.0.32
Microsoft Windows Server 2022<10.0.20348.5761
10.0.20348.5761
Microsoft Visual Studio 2026=18.10
18.10.4
Microsoft Windows 11=23H2
10.0.22631.7652
Microsoft Windows 11=26H1
10.0.28000.3231
Microsoft Windows Server 2022<10.0.20348.5761
10.0.20348.5761
Microsoft Windows 11=25H2
10.0.26200.9711
Microsoft Windows 11=24H2
10.0.26100.9711
Microsoft Windows 11=23H2
10.0.22631.7652
nuget/Microsoft.Native.Quic.MsQuic.Schannel=2.5.11-ci.156755675
2.5.11-ci.159417053

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 10.0.26300.9711Patch KB5127648
  2. Upgrade

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

    Fixed in 10.0.26100.9711Patch KB5127648
  3. Upgrade

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

    Fixed in 10.0.26200.9711Patch KB5127648
  4. Upgrade

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

    Fixed in 11.0.0-rc.2.26504.105
  5. Upgrade

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

    Fixed in 10.0.26100.33650Patch KB5126646
  6. Upgrade

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

    Fixed in 9.0.21
  7. Upgrade

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

    Fixed in 10.0.28000.3231Patch KB5127646
  8. Upgrade

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

    Fixed in 10.0.14
  9. Upgrade

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

    Fixed in 17.14.42
  10. Upgrade

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

    Fixed in 10.0.20348.5761Patch KB5126655
  11. Upgrade

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

    Fixed in 18.10.4
  12. Upgrade

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

    Fixed in 8.0.32
  13. Upgrade

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

    Fixed in 10.0.22631.7652Patch KB5126653
  14. Upgrade

    Upgrade nuget/Microsoft.Native.Quic.MsQuic.Schannel to a version that resolves this vulnerability.

    Fixed in 2.5.11-ci.159417053
  15. Upgrade

    Upgrade Microsoft.Native.Quic.MsQuic.Schannel to a version that resolves this vulnerability.

    Fixed in 2.5.11-ci.159417053
  16. Operational

    Recompile and redeploy self-contained applications targeting the impacted .NET versions.

  17. 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:01 PM
Data Sourced
via MITRE·07:01 PM
DescriptionSeverity
Data Sourced
via NVD·07:17 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·07:56 PM
Data Sourced
via GitHub·07:56 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Which systems should be prioritized for remediation?

Prioritize Microsoft Windows 11, Windows Server 2022, Windows Server 2025, and Windows systems with Microsoft QUIC, .NET 9.0, .NET 10.0, .NET 11.0, or Visual Studio 2022 listed as affected software.

2

Does exploitation require authentication or user interaction?

No. The supplied vector indicates network-based exploitation with low attack complexity, no privileges required, and no user interaction required.

3

What impact could successful exploitation have?

An attacker could execute code remotely. The provided severity vector indicates high impact to confidentiality, integrity, and availability.

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