← Back

CVE-2026-32157

nvd nist
Published: Apr 14, 2026Modified: Jun 17, 2026

JSON object

Loading...
8.8
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Exploitability: 2.8 / Impact: 5.9
Source: secure@microsoft.com (Secondary)

Description

Use after free in Remote Desktop Client allows an unauthorized attacker to execute code over a network.

Affected (25)

Microsoft
15 products
Remote Desktop Client
Windows 10 1607
Windows 10 1809
Windows 10 21h2
Windows 10 22h2
Windows 11 23h2
Windows 11 24h2
Windows 11 25h2
Windows 11 26h1
Windows Server 2012
Windows Server 2016
Windows Server 2019
Windows Server 2022
Windows Server 2022 23h2
Windows Server 2025
Configuration A
25 vulnerable
Vulnerable SoftwareAffected Versions
Remote Desktop Client
Before 2.0.1070.0
Microsoft
Windows 10 1607
Before 10.0.14393.9060
Windows 10 1607
Before 10.0.14393.9060
Microsoft
Windows 10 1809
Before 10.0.17763.8644
Windows 10 1809
Before 10.0.17763.8644
Microsoft
Windows 10 21h2
Before 10.0.19044.7184
Windows 10 21h2
Before 10.0.19044.7184
Windows 10 21h2
Before 10.0.19044.7184
Microsoft
Windows 10 22h2
Before 10.0.19045.7184
Windows 10 22h2
Before 10.0.19045.7184
Microsoft
Windows 11 23h2
Before 10.0.22631.6936
Windows 11 23h2
Before 10.0.22631.6936
Microsoft
Windows 11 24h2
Before 10.0.26100.8246
Windows 11 24h2
Before 10.0.26100.8246
Microsoft
Windows 11 25h2
Before 10.0.26200.8246
Windows 11 25h2
Before 10.0.26200.8246
Microsoft
Windows 11 26h1
Before 10.0.28000.1836
Windows 11 26h1
Before 10.0.28000.1836
Microsoft
Windows Server 2012
All versions
Windows Server 2012
Version r2
Windows Server 2016
Before 10.0.14393.9060
Windows Server 2019
Before 10.0.17763.8644
Windows Server 2022
Before 10.0.20348.5020
Windows Server 2022 23h2
Before 10.0.25398.2274
Windows Server 2025
Before 10.0.26100.32690

Related CWEs

CWE-416
Use After Free
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)

Source: secure@microsoft.com
Vendor Advisory

Timeline

No history available yet.