Skip to main content
VulnerabilityPublished

CVE-2026-105794: microsoft msquic · Improper Certificate Validation

Affects microsoft msquicSource CVE Database V5

0
Compare

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

CVSS 4.0 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
microsoftmsquicAffected
  • >=2.6.0 <2.6.1
Fixed in
  • 2.6.1
microsoftmsquicAffected
  • >=2.5.0 <2.5.11
Fixed in
  • 2.5.11
microsoftmsquicAffected
  • <2.4.20
Fixed in
  • 2.4.20
GitHubmicrosoft/msquicpkg:github/microsoft/msquicOther threatsAffected
  • <2.4.20
  • >=2.5.0 <2.5.11
  • >=2.6.0 <2.6.1
Fixed in
  • 2.4.20
  • 2.5.11
  • 2.6.1

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

Community reviews

Loading reviews…