Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 10.0amended

Microsoft QUIC: Remote Code Execution Vulnerability

CVE-2026-62815GHSA-92f5-vc22-8j33

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (microsoft.native.quic.msquic.schannel 2.5.10, 2.4.19; microsoft.native.quic.msquic.openssl 2.5.10, 2.4.19), 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.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
10.0 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H · score source
EPSS
  • CVE-2026-62815: 0.97% estimated exploitation activity in the next 30 days; percentile 62.12 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary Use after free in Microsoft QUIC allows an unauthorized attacker to execute code over a network. Details New network path creations and removals triggered by incoming packets can lead to a pointer invalidation. Patches - Guard path promotion e0f55b5 Impact An unauthenticated attacker could exploit this vulnerability by sending a specially crafted packet to an affected service over the network. Successful exploitation could allow the attacker to execute code on the target system. No authentication or user interaction is required.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-92f5-vc22-8j33

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-92f5-vc22-8j33

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-62815

Advisory: Microsoft QUIC: Remote Code Execution Vulnerability
IDs: CVE-2026-62815, GHSA-92f5-vc22-8j33
Record: https://patchnext.com/advisories/cve-2026-62815 (revision 3, source checked 26 Oct 2026, 17:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 10.0)
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.5.10, 2.4.19; microsoft.native.quic.msquic.openssl 2.5.10, 2.4.19. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet microsoft.native.quic.msquic.schannel: affected >= 2.5.3, < 2.5.10; < 2.4.19; fixed in 2.4.19, 2.5.10
- NuGet microsoft.native.quic.msquic.openssl: affected >= 2.5.3, < 2.5.10; < 2.4.19; fixed in 2.4.19, 2.5.10

## 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://osv.dev/vulnerability/GHSA-92f5-vc22-8j33 (OSV record GHSA-92f5-vc22-8j33 lists affected ranges: NuGet microsoft.native.quic.msquic.openssl >=2.5.3 =0 =2.5.3 =0 <2.4.19 (fixed))
- Verified: https://github.com/advisories/GHSA-92f5-vc22-8j33 (GitHub-reviewed advisory GHSA-92f5-vc22-8j33 lists affected ranges: NuGet microsoft.native.quic.msquic.openssl >=2.5.3 =0 =2.5.3 =0 <2.4.19)

Commands are suggestions: review each one before running it.

Loading voting…