CVE-2026-85790

Published: Oct 13, 2026Modified: Oct 22, 2026

5.9

Vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitability: 2.2 / Impact: 3.6

Source: secure@microsoft.com (Secondary)

Description

Use after free in Microsoft QUIC allows an unauthorized attacker to disclose information over a network.

Affected (15)

Products: Microsoft: Windows 11 23h2, Windows 11 24h2, Windows 11 25h2, Windows 11 26h1, Windows 11 26h2, Windows Server 2022, Windows Server 2025, Native.quic.msquic.schannel, Visual Studio 2022, Visual Studio 2026

10 products

Windows 11 23h2

Windows 11 24h2

Windows 11 25h2

Windows 11 26h1

Windows 11 26h2

Windows Server 2022

Windows Server 2025

Native.quic.msquic.schannel

Visual Studio 2022

Visual Studio 2026

Configuration A

12 vulnerable

Vulnerable Software	Affected Versions
Microsoft Windows 11 23h2	version < 10.0.22631.7652
Microsoft Windows 11 23h2	version < 10.0.22631.7652
Microsoft Windows 11 24h2	version < 10.0.26100.9711
Microsoft Windows 11 24h2	version < 10.0.26100.9711
Microsoft Windows 11 25h2	version < 10.0.26200.9711
Microsoft Windows 11 25h2	version < 10.0.26200.9711
Microsoft Windows 11 26h1	version < 10.0.28000.3231
Microsoft Windows 11 26h1	version < 10.0.28000.3231
Microsoft Windows 11 26h2	version < 10.0.26300.9711
Microsoft Windows 11 26h2	version < 10.0.26300.9711
Microsoft Windows Server 2022	version < 10.0.20348.5761
Microsoft Windows Server 2025	version < 10.0.26100.33650

Configuration B

1 vulnerable · 4 platform

Vulnerable Software	Affected Versions
Microsoft Native.quic.msquic.schannel	version < 2.6.2

Running on/with	Platform Versions
Microsoft .net	Version 10.0.0
Microsoft .net	Version 11.0.0
Microsoft .net	Version 8.0.0
Microsoft .net	Version 9.0.0

Configuration C

2 vulnerable

Vulnerable Software	Affected Versions
Microsoft Visual Studio 2022	17.14.0 ≤ version < 17.14.42
Microsoft Visual Studio 2026	18.10.0 ≤ version < 18.10.4

Related CWEs

The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

References (1)

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-85790

Source: secure@microsoft.com

PatchVendor Advisory

Timeline

No history available yet.