Remote Denial of Service Vulnerability in Microsoft QUIC
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (microsoft.native.quic.msquic.schannel 2.3.5, 2.2.7, 2.1.12; microsoft.native.quic.msquic.openssl 2.3.5, 2.2.7, 2.1.12), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
NuGet microsoft.native.quic.msquic.schannel
- Affected
- >= 2.2.0, < 2.2.7>= 2.3.0, < 2.3.5< 2.1.12
- Fixed in
- 2.1.12, 2.2.7, 2.3.5
NuGet microsoft.native.quic.msquic.openssl
- Affected
- < 2.1.12>= 2.2.0, < 2.2.7>= 2.3.0, < 2.3.5
- Fixed in
- 2.1.12, 2.2.7, 2.3.5
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-2x7m-gf85-3745 lists affected ranges: NuGet microsoft.native.quic.msquic.openssl >=0 =2.2.0 =2.3.0 =2.2.0 =2.3.0 =0 <2.1.12
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
Impact The MsQuic server will continue to leak memory until no more is available, resulting in a denial of service. Patches The following patch was made: - Fix Memory Leak from Multiple Decodes of TP - https://github.com/microsoft/msquic/commit/5d070d661c45979946615289e92bb6b822efe9e9 Workarounds Beyond upgrading to the patched versions, there is no other workaround. MSRC CVE Info https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-26190
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-2x7m-gf85-3745
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-2x7m-gf85-3745 Advisory: Remote Denial of Service Vulnerability in Microsoft QUIC IDs: GHSA-2x7m-gf85-3745 Record: https://patchnext.com/advisories/ghsa-2x7m-gf85-3745 (revision 1, source checked 26 Oct 2026, 17:00 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: microsoft.native.quic.msquic.schannel 2.3.5, 2.2.7, 2.1.12; microsoft.native.quic.msquic.openssl 2.3.5, 2.2.7, 2.1.12. A vendor fix does not mean a deployment is fixed. ## Affected components - NuGet microsoft.native.quic.msquic.schannel: affected >= 2.2.0, < 2.2.7; >= 2.3.0, < 2.3.5; < 2.1.12; fixed in 2.1.12, 2.2.7, 2.3.5 - NuGet microsoft.native.quic.msquic.openssl: affected < 2.1.12; >= 2.2.0, < 2.2.7; >= 2.3.0, < 2.3.5; fixed in 2.1.12, 2.2.7, 2.3.5 ## Suggested inspection (read-only) - NuGet microsoft.native.quic.msquic.schannel: check the installed version with your package manager. - NuGet microsoft.native.quic.msquic.openssl: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on microsoft.native.quic.msquic.schannel, microsoft.native.quic.msquic.openssl. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-2x7m-gf85-3745 (GitHub-reviewed advisory GHSA-2x7m-gf85-3745 lists affected ranges: NuGet microsoft.native.quic.msquic.openssl >=0 =2.2.0 =2.3.0 =2.2.0 =2.3.0 =0 <2.1.12) Commands are suggestions: review each one before running it.
Loading voting…