cve.bz

CVE-2026-105794 microsoft msquic: Improper Certificate Validation

9.1 criticalEPSS 1.0%Fix available

Critical (9.1) in microsoft msquic. EPSS 1.0% estimated probability of exploitation activity in the next 30 days. Fixed in Microsoft.Native.Quic.MsQuic.OpenSSL 2.4.20, 2.5.11, 2.6.1.

On this page
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.

Severity

CVSS 4.0

9.1 critical
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
EPSS
1.0% (unchanged from 1.0% a week ago; 1.0% 30 days ago) estimated probability of exploitation activity in the next 30 days; 63rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-295 Improper Certificate Validation
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Microsoft.Native.Quic.MsQuic.OpenSSL (NuGet): fixed in 2.4.20, 2.5.11, 2.6.1

Ask an AI about this CVE

Show the promptExplain CVE-2026-105794 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-105794?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-105794?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-105794 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
microsoft msquic< 2.4.20
microsoft msquic>= 2.5.0, < 2.5.11
microsoft msquic>= 2.6.0, < 2.6.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-w5f4-fx9m-m4q7NuGetMicrosoft.Native.Quic.MsQuic.OpenSSL<2.4.202.4.20
GHSA-w5f4-fx9m-m4q7NuGetMicrosoft.Native.Quic.MsQuic.OpenSSL>=2.5.0 <2.5.112.5.11
GHSA-w5f4-fx9m-m4q7NuGetMicrosoft.Native.Quic.MsQuic.OpenSSL>=2.6.0 <2.6.12.6.1

Attack patterns (CAPEC)

  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON