Skip to content
Fencer Vulns
critical 9.8

CVE-2026-62815 json

Microsoft QUIC Remote Code Execution Vulnerability

published 2026-08-11 2 mo ago modified 2026-10-30 9 d ago also GHSA-92f5-vc22-8j33 , EUVD-2026-56392

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 62%
public exploits
0
none known

Summary

Use after free in Microsoft QUIC allows an unauthorized attacker to execute code over a network.

Patch / fix

  • nuget Microsoft.Native.Quic.MsQuic.OpenSSL 2.4.19, 2.5.10
  • nuget Microsoft.Native.Quic.MsQuic.Schannel 2.4.19, 2.5.10
  • Microsoft Windows 11 version 23H2 10.0.22631.7517
  • Microsoft Windows 11 Version 24H2 10.0.26100.9168
  • Microsoft Windows 11 Version 25H2 10.0.26200.9168
  • Microsoft Windows 11 version 26H1 10.0.28000.2704
  • Microsoft Windows Server 2022 10.0.20348.5499
  • Microsoft Windows Server 2025 10.0.26100.33296
  • Microsoft Windows Server 2025 (Server Core installation) 10.0.26100.33296

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
3 mo ago

Exploit prediction

0.97% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
nuget Microsoft.Native.Quic.MsQuic.OpenSSL
>=2.5.3, <2.5.10
<2.4.19
2.5.10
2.4.19
nuget Microsoft.Native.Quic.MsQuic.Schannel
>=2.5.3, <2.5.10
<2.4.19
2.5.10
2.4.19

Affected products

  • Microsoft Windows 11 version 23H2
  • Microsoft Windows 11 Version 24H2
  • Microsoft Windows 11 Version 25H2
  • Microsoft Windows 11 version 26H1
  • Microsoft Windows Server 2022
  • Microsoft Windows Server 2025
  • Microsoft Windows Server 2025 (Server Core installation)

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.