Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

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

CVSS 4.0 9.1 CRITICALEUVD CVSS 4.0 9.1 CVSS 4.0 · [email protected] · Secondary 9.1 CRITICALCVSS_V4 Publisher rating CRITICALFixed by Microsoft.Native.Quic.MsQuic.OpenSSL 2.4.20Fixed by Microsoft.Native.Quic.MsQuic.OpenSSL 2.5.11Fixed by Microsoft.Native.Quic.MsQuic.OpenSSL 2.6.1KEV status unknown

cve-program · CVE-2026-105794

Published

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.

Read the publisher's advisory

euvd · EUVD-2026-93422

Published

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.

Read the publisher's advisory

nvd · CVE-2026-105794

Published

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.

Read the publisher's advisory

osv · GHSA-w5f4-fx9m-m4q7

Published

# Summary Improper TLS hostname verification allows a man-in-the-middle (MITM) attack on MsQuic. # Details Only MsQuic with the OpenSSL and QuicTLS TLS backends is affected (the Schannel backend is not affected). ## Patches 2.6.1, 2.5.11, and 2.4.20 # Impact An on-path attacker could spoof a server identity by using a certificate that doesn't match the intended target server hostname.

Read the publisher's advisory

Affected versions, risk and source history

Related advisories and sources

Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.

CVE-2026-105794 · CVE overview and exploitation status

EUVD-2026-93422

GHSA-w5f4-fx9m-m4q7

cve-program · CVE-2026-105794

euvd · EUVD-2026-93422

nvd · CVE-2026-105794

osv · GHSA-w5f4-fx9m-m4q7

Related changes

Linked by CVE identifier

No related changes are available here.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 22 Nov 09:08 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current