CVE-2026-105794: microsoft msquic · Improper Certificate Validation
Affects microsoft msquicSource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical · fixed in 2.6.1 : patch microsoft msquic as a priority.
Data as of 20 Nov 2026, 17:34 UTC
- EPSS
- 1.0% chance of exploitation in 30 days – higher than 63% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.6.1, 2.5.11, 2.4.20
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 6 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade msquic and microsoft/msquic to 2.6.1, 2.5.11 or 2.4.20.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| microsoftmsquic | Affected
| Fixed in
|
| microsoftmsquic | Affected
| Fixed in
|
| microsoftmsquic | Affected
| Fixed in
|
GitHubmicrosoft/msquicpkg:github/microsoft/msquicOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade MsQuic to version 2.4.20, 2.5.11, or 2.6.1 or later, where this certificate validation issue is fixed. No other mitigation is indicated. Since this is a client-side vulnerability, applying the official patches is the recommended remediation.
Description
MsQuic is a cross-platform C implementation of the IETF QUIC protocol exposed to C, C++, C#, and Rust. Prior to 2.4.20, 2.5.11, and 2.6.1, MsQuic clients using the OpenSSL or QuicTLS TLS backend do not properly verify that a server certificate matches the intended target server hostname. An on-path attacker can therefore present a certificate that does not match the intended target hostname and spoof the server in a man-in-the-middle attack. The Schannel backend is not affected. This issue is fixed in versions 2.4.20, 2.5.11, and 2.6.1.
References
- github.com/microsoft/msquic/security/advisories/GHSA-w5f4-fx9m-m4q7 (opens in a new tab)
- github.com/microsoft/msquic/pull/6274 (opens in a new tab)
- github.com/microsoft/msquic/pull/6275 (opens in a new tab)
- github.com/microsoft/msquic/pull/6276 (opens in a new tab)
- github.com/microsoft/msquic/pull/6277 (opens in a new tab)
- github.com/microsoft/msquic/commit/0591586443cc73a2d2cfb679527d91a144b4a412 (opens in a new tab)
- github.com/microsoft/msquic/commit/508e811370df93e2ad848f5c78347d4fe4f65a91 (opens in a new tab)
- github.com/microsoft/msquic/commit/90fd45498bf9b506b8556fb407088688474d6c81 (opens in a new tab)
- github.com/microsoft/msquic/commit/a01333cf7c2659cce0ff03ef3f21e1ff15bb5b83 (opens in a new tab)
- github.com/microsoft/msquic/releases/tag/v2.4.20 (opens in a new tab)
- github.com/microsoft/msquic/releases/tag/v2.5.11 (opens in a new tab)
- github.com/microsoft/msquic/releases/tag/v2.6.1 (opens in a new tab)