Skip to content
← Blog · · df00tech

Critical Microsoft QUIC Flaw (CVE-2026-105016) Enables Unauthenticated RCE in .NET 8/9/10/11 on Windows

breaking ghsa nuget CVE-2026-105016

Microsoft has published a security advisory for CVE-2026-105016, a critical remote code execution vulnerability in Microsoft QUIC (MsQuic) as used by .NET 8.0, .NET 9.0, .NET 10.0, and .NET 11 RC2 on Windows. According to the advisory, a crafted IPv6 QUIC packet can reach the HTTP/3 path without authentication or user interaction and trigger RCE via a heap-based buffer overflow (CWE-122). The issue is tracked through the Microsoft.Native.Quic.MsQuic.Schannel NuGet package, affecting version 2.5.11-ci.156755675, with a fix in 2.5.11-ci.159417053. The advisory carries a CVSS 3.1 score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), and a proof-of-concept is reported as publicly available; the finding is credited to researcher "pwn2addr."

Why it matters

This is about as severe as a vulnerability gets: no authentication, no user interaction, network-reachable, and full compromise (confidentiality, integrity, and availability impact). Any Windows application or service that uses HTTP/3 via the Microsoft QUIC implementation bundled with affected .NET runtimes is exposed — including self-contained deployments that bundle the vulnerable package and won't pick up a runtime-only patch. Given the public PoC, the window between disclosure and opportunistic exploitation attempts could be short.

What defenders should do now

  • Inventory Windows hosts running .NET 8/9/10 (or .NET 11 RC2) services that enable HTTP/3/QUIC, and check for direct references to Microsoft.Native.Quic.MsQuic.Schannel.
  • Apply the latest .NET servicing update for your supported release, or bump the package reference to 2.5.11-ci.159417053 or later; restart affected applications afterward.
  • Identify and recompile/redeploy any self-contained deployments built against the vulnerable package — a runtime patch alone won't fix these.
  • If immediate patching isn't possible, consider disabling HTTP/3/QUIC support on exposed endpoints as a stopgap, and review firewall/IPv6 exposure for services that accept untrusted IPv6 traffic.
  • Hunting angle: watch for anomalous or malformed IPv6 QUIC traffic, unexpected crashes/restarts of .NET services using HTTP/3, and new or unexpected child processes spawned from .NET web server processes.

This is developing intel based on a same-day advisory; details on in-the-wild exploitation may evolve. For the full technical advisory, affected package details, and remediation guidance, see the original GitHub Security Advisory: GHSA-5gjq-3f94-rcf7.

Detections in this post

  • CVE-2026-105016 — Microsoft QUIC (MsQuic Schannel) Heap-Based Buffer Overflow Remote Code Execution (CVE-2026-105016)

Get new detections in your inbox

New ATT&CK coverage plus CISA KEV / CVE detection rules, roughly weekly. No spam, unsubscribe anytime.