Abstract illustration of connected devices separated by a protected security boundary.
Patching infrastructure servers rarely feels glamorous, right up until an unassuming memory bug hands over the keys to an entire host. Microsoft has published an official security advisory through the Microsoft Security Response Center (MSRC) addressing CVE-2026-69565, formally titled Windows Remote Desktop Services Remote Code Execution Vulnerability. Rated Important in severity with a CVSS base score of 7.0 and a CVSS temporal score of 6.1, this flaw stems from a memory corruption weakness in the Remote Desktop Gateway Service across four supported generations of Windows Server: 2016, 2019, 2022, and 2025. While the advisory carries a "Remote Code Execution" classification in its formal title, a closer look at Microsoft's technical metrics reveals a nuanced post-authentication threat profile where an authorized local attacker must win a complex race condition to achieve SYSTEM privileges.

For Windows Server administrators managing Remote Desktop infrastructure, terminal farms, or bastion hosts, understanding the exact mechanics of this patch—and why a local attack vector wears an RCE label—is critical for accurate risk prioritization during your maintenance window.

Abstract illustration of connected devices separated by a protected security boundary. Vulnerability Snapshot and Official MSRC Telemetry​

Before diving into how memory management mishaps affect multi-user gateway servers, let us review the authoritative technical identifiers and status indicators published by Microsoft for CVE-2026-69565:

  • CVE Identifier: CVE-2026-69565
  • Title: Windows Remote Desktop Services Remote Code Execution Vulnerability
  • Secondary Advisory Designation: Remote Desktop Gateway Service Remote Code Execution Vulnerability
  • Official Description: Use after free in Remote Desktop Gateway Service allows an authorized attacker to execute code locally.
  • Severity: Important
  • Weakness Classification: CWE-416 (Use After Free)
  • CVSS Base Score: 7.0
  • CVSS Temporal Score: 6.1
  • CVSS Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
  • Publicly disclosed: No
  • Exploited: No
  • Exploitation Assessment: Exploitation Less Likely
  • Customer action required: Yes

Every non-zero metric in that CVSS v3.1 vector tells an essential part of the operational story. Let us unpack why this specific combination of flags matters in production environments.

Section Summary​

CVE-2026-69565 is an Important-rated CWE-416 use-after-free vulnerability in the Remote Desktop Gateway Service with a 7.0 base score, 6.1 temporal score, no known public disclosure or active exploitation, and mandatory customer patching across affected Windows Server editions.


Decoding the Technical Mechanics: Why Does an "RCE" Require Local Access?​

If you have spent enough years reading Patch Tuesday bulletins, you have probably noticed an occasional quirk in vulnerability naming: a bug titled Windows Remote Desktop Services Remote Code Execution Vulnerability (and referenced in advisory notes as Remote Desktop Gateway Service Remote Code Execution Vulnerability) that explicitly states: Use after free in Remote Desktop Gateway Service allows an authorized attacker to execute code locally.

Why the apparent contradiction between "Remote" in the title and AV:L (Attack Vector: Local) in the CVSS string? Based on general industry knowledge of vulnerability taxonomy and CVSS scoring, security advisories frequently categorize arbitrary code execution flaws within network-facing daemon processes under the broad umbrella of RCE—distinguishing full code execution in a target service's memory space from constrained logic privilege escalations—even when triggering the vulnerable code path requires an established local session or low-privileged local execution context (PR:L).

Here is what the official MSRC advisory facts establish about how CVE-2026-69565 actually behaves under the hood:

  1. The Underlying Flaw (CWE-416): A use-after-free condition occurs when a program allocates a block of heap memory, frees that memory back to the allocator when an object is no longer needed, and then mistakenly continues to reference the dangling pointer. If an attacker can groom memory so that malicious data occupies that newly freed slot before the stale pointer is dereferenced, the service can be tricked into executing arbitrary instructions.
  2. The Ultimate Prize (SYSTEM Control): In its official advisory FAQ, Microsoft addresses the exact impact: What privileges could be gained by an attacker who successfully exploited this vulnerability? An attacker who successfully exploited this vulnerability could gain SYSTEM privileges. Because Confidentiality (C:H), Integrity (I:H), and Availability (A:H) are all rated High with Unchanged Scope (S:U), winning this exploit means total takeover of the underlying Windows Server operating system.
  3. High Attack Complexity (AC:H) and Race Conditions: Turning a use-after-free bug into reliable code execution is rarely trivial, and Microsoft provides two distinct explanations for why AC:H applies here. First, Microsoft notes that successful exploitation requires an attacker to have a deep understanding of the system, adding that success is not guaranteed and depends on a combination of factors that might include the environment, system configuration, and the presence of additional security measures. Second, Microsoft explicitly confirms that successful exploitation of this vulnerability requires an attacker to win a race condition.

Think of a race condition in a multi-threaded service like trying to swap a folder on a busy clerk's desk in the exact microsecond between when they put their pen down and when they stamp the page. Move too early, and nothing happens; move too late, or collide with modern Windows heap mitigations, and you crash the service process instead of hijacking it. No user interaction is needed (UI:N), and the temporal vector (E:U/RL:O/RC:C) reflects unproven exploit maturity alongside an official remediation patch and confirmed report confidence.

Section Summary​

Despite carrying an RCE title, CVE-2026-69565 requires local access (AV:L) and low privileges (PR:L), with no user interaction (UI:N). To achieve SYSTEM privileges via this CWE-416 use-after-free bug, an authorized attacker must possess deep system knowledge, navigate environmental and security mitigations, and win a timing-sensitive race condition (AC:H).


Real-World Server Risk: Where Remote Desktop Gateway Fits In​

Why should IT teams care about a local, high-complexity bug rated Exploitation Less Likely? Because Remote Desktop Gateway servers sit at the crossroads of enterprise access.

Synthesizing from general Windows infrastructure administration experience, Remote Desktop Gateway encapsulates Remote Desktop Protocol traffic inside HTTPS tunnels so remote staff, contractors, or administrators can reach internal resources without exposing raw RDP ports directly to the public internet. In smaller deployments or consolidated branch architectures, a server running the Remote Desktop Gateway Service may also host co-located roles, management agents, scheduled maintenance scripts, or restricted administrative sessions.

Consider a realistic defense-in-depth scenario: suppose a threat actor compromises a low-privileged service account or gains restricted local command execution on a Windows Server box via a misconfigured web application or stolen credential. At that stage, the attacker is boxed in by standard Windows user permissions. However, if the Remote Desktop Gateway Service is present and unpatched, CVE-2026-69565 represents a potential privilege escalation bridge straight to SYSTEM. Once an adversary attains SYSTEM on an RD Gateway host, they can inspect session metadata, harvest credentials in memory (depending on virtualization-based security protections), manipulate gateway authorization policies, or pivot deeper into the corporate network.

On the balanced side of risk analysis, administrators do not need to hit the panic button or pull emergency midnight outages if standard change control is already scheduled soon. With Publicly disclosed: No, Exploited: No, and Microsoft's Exploitation Less Likely assessment, there is no active wildfire burning through enterprise datacenters today. Instead, this is textbook hygiene: patch methodically during your regular security update cycle so that CVE-2026-69565 never matures into a post-exploitation stepping stone.

Section Summary​

While CVE-2026-69565 is neither exploited in the wild nor publicly disclosed, unpatched Remote Desktop Gateway servers remain high-value infrastructure targets where an already-authenticated attacker could attempt to leverage the flaw to jump from low privileges to SYSTEM.


Affected Products, KB Updates, and Fixed Build Matrix​

Microsoft has issued official security updates (Customer action required: Yes) across both full Desktop Experience and Server Core x64 installations of Windows Server 2016, Windows Server 2019, Windows Server 2022, and Windows Server 2025. Notice in particular that Windows Server 2025 has two distinct KB-to-build update paths documented in the MSRC contract.

Affected ProductRequired KB ArticleVendor Fixed Build
Windows Server 2016 (Server Core installation) (x64)KB513129110.0.14393.9688
Windows Server 2016 (x64)KB513129110.0.14393.9688
Windows Server 2019 (Server Core installation) (x64)KB513108510.0.17763.9487
Windows Server 2019 (x64)KB513108510.0.17763.9487
Windows Server 2022 (Server Core installation) (x64)KB513109010.0.20348.5870
Windows Server 2022 (x64)KB513109010.0.20348.5870
Windows Server 2025 (Server Core installation) (x64)KB513107710.0.26100.33730
Windows Server 2025 (Server Core installation) (x64)KB513108010.0.26100.33822
Windows Server 2025 (x64)KB513107710.0.26100.33730
Windows Server 2025 (x64)KB513108010.0.26100.33822

Exact Official Remediation Requirements​

To ensure complete alignment with MSRC compliance verification across your fleet, apply the exact remediation guidance corresponding to each operating system edition:

  • For Windows Server 2016 (Server Core installation) (x64), install KB5131291 to reach fixed build 10.0.14393.9688.
  • For Windows Server 2016 (x64), install KB5131291 to reach fixed build 10.0.14393.9688.
  • For Windows Server 2019 (Server Core installation) (x64), install KB5131085 to reach fixed build 10.0.17763.9487.
  • For Windows Server 2019 (x64), install KB5131085 to reach fixed build 10.0.17763.9487.
  • For Windows Server 2022 (Server Core installation) (x64), install KB5131090 to reach fixed build 10.0.20348.5870.
  • For Windows Server 2022 (x64), install KB5131090 to reach fixed build 10.0.20348.5870.
  • For Windows Server 2025 (Server Core installation) (x64), install KB5131077 to reach fixed build 10.0.26100.33730; install KB5131080 to reach fixed build 10.0.26100.33822.
  • For Windows Server 2025 (x64), install KB5131077 to reach fixed build 10.0.26100.33730; install KB5131080 to reach fixed build 10.0.26100.33822.

Section Summary​

Administrators running Windows Server 2016, 2019, 2022, or 2025—in either standard x64 or Server Core x64 installations—must deploy their respective cumulative security updates (KB5131291, KB5131085, KB5131090, KB5131077, or KB5131080) and verify the resulting OS build numbers to remediate CVE-2026-69565.


Step-by-Step Deployment and Verification Checklist for Sysadmins​

Drawing on standard Windows Server patch management practices, rolling out updates to Remote Desktop Gateway servers requires a little extra choreography so you do not abruptly drop active user tunnels mid-workday. Follow this practical workflow to patch cleanly and prove compliance:

  1. Inventory Affected Hosts: Identify all Windows Server 2016, 2019, 2022, and 2025 instances in your environment—paying special attention to hosts with the Remote Desktop Gateway role installed, as well as golden VM templates where the role might be enabled later.
  2. Drain Active Gateway Connections: If your RD Gateway farm sits behind a load balancer, place one gateway node into drain mode at a time so existing HTTPS-encapsulated sessions finish gracefully while new connections route to healthy peers.
  3. Apply the Security Update: Deploy the applicable KB package (KB5131291, KB5131085, KB5131090, KB5131077, or KB5131080) via Windows Server Update Services (WSUS), Microsoft Configuration Manager, Azure Update Manager, or manual update packages, and complete the required system reboot.
  4. Verify Exact Build Numbers: On both Desktop Experience and headless Server Core machines, open an elevated PowerShell prompt or remote management session and check the OS build and revision level (for example, inspecting [System.Environment]::OSVersion.Version alongside the UBR registry value under HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion) to confirm your server matches or exceeds 10.0.14393.9688, 10.0.17763.9487, 10.0.20348.5870, 10.0.26100.33730, or 10.0.26100.33822.
  5. Audit Local Access Hygiene: Because CVE-2026-69565 requires an authorized local foothold (AV:L/PR:L), review who is permitted to log on locally or run services on your RD Gateway servers. Dedicated gateway hosts should restrict interactive local logons strictly to tier-appropriate server administrators.

If you are tracking broader Windows Server security patches, cumulative update behavior, or Remote Desktop hardening strategies, check out our ongoing enterprise administration discussions across WindowsForum.com to compare deployment notes with fellow sysadmins.

Section Summary​

By draining active gateway sessions on load-balanced nodes, installing the designated KB updates, verifying exact post-reboot build numbers, and tightening local logon rights, administrators can neutralize CVE-2026-69565 without disrupting remote workforces.

 

References

  1. Official MSRC or vendor evidence msrc.microsoft.com
  2. Official MSRC or vendor evidence api.msrc.microsoft.com
  3. Official MSRC or vendor evidence api.msrc.microsoft.com