CVE-2026-105794

MsQuic: Improper Certificate Validation in Microsoft.Native.Quic.MsQuic.OpenSSL

Published Oct 6, 2026 CVSS 4.0 · 9.1 Critical EPSS 1.0% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

MsQuic clients that use the OpenSSL or QuicTLS TLS backends failed to verify that a server certificate matches the intended target hostname, allowing an attacker to present a fraudulent certificate and impersonate the server. This flaw enables a man‑in‑the‑middle attack without the need for privileged access or code execution on the client machine.

Affected Systems

Affected systems include Microsoft MsQuic prior to release 2.4.20, 2.5.11, and 2.6.1 when using OpenSSL or QuicTLS backends. The Schannel backend is not vulnerable. The issue is fixed in the three mentioned releases.

Risk and Exploitability

The CVSS base score of 9.1 indicates critical severity, while the EPSS score of 1% suggests that exploitation is currently rare but not impossible. The flaw is not listed in the CISA KEV catalog. An attacker who can position themselves as an on‑path entity can perform a man‑in‑the‑middle attack by presenting a fraudulent certificate that bypasses hostname validation. The vulnerability is exploitable remotely over any network that permits interception of the TLS handshake, making it highly relevant to public‑facing services using MsQuic without the latest patches.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade MsQuic to version 2.4.20, 2.5.11, or 2.6.1 and deploy the updated binaries or libraries
  • Verify that the OpenSSL or QuicTLS backend is configured to enforce hostname verification for client certificates, and that the target hostname matches the server certificate domain
  • If an upgrade cannot be applied immediately, switch the MsQuic configuration to use the Schannel backend, which is not affected by this flaw

Generated by OpenCVE AI on October 7, 2026 at 14:43 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-w5f4-fx9m-m4q7 MsQuic: Improper Certificate Validation in Microsoft.Native.Quic.MsQuic.OpenSSL
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Microsoft
Microsoft msquic
Vendors & Products Microsoft
Microsoft msquic
Type Values Removed Values Added
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.
Title MsQuic: Improper Certificate Validation in Microsoft.Native.Quic.MsQuic.OpenSSL
Weaknesses CWE-295
References
Metrics cvssV4_0

{'score': 9.1, 'vector': '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'}

Weaknesses
  • CWE-295

    Improper Certificate Validation

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 6, 2026, 5:40 PM
Reserved
Oct 5, 2026, 8:37 PM
Status
Awaiting Analysis
Published
Oct 6, 2026, 3:17 PM
Modified
Oct 6, 2026, 6:16 PM