Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify internet-facing RD Gateway
-
DeliverySend repeated crafted connection requests
-
ExploitTrigger unreleased memory allocations (CWE-401)
-
ExecutionExhaust server memory resources
-
ImpactDeny service to legitimate remote users
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Resource cleanup, leak prevention
|
| Exploitation Conditions | Exploitation requires the target host to have the Remote Desktop Gateway (RD Gateway) role service installed, running, and reachable over the network - this is not present on default Windows Server installs, so only servers deliberately configured as RD Gateways are affected. Where that role is deployed (frequently internet-facing on TCP 443 to broker remote desktop sessions), the CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates no authentication, no credentials, and no user interaction are needed to trigger the memory leak. Limiting factors: the attack affects availability only (no data exposure or code execution), impact is cumulative/resource-exhaustion rather than instantaneous, and exposure is bounded to hosts running the RD Gateway role within the enumerated unpatched Windows Server build ranges. |
| Impact | Signals converge on a moderate, availability-only risk. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5 HIGH) describes a remote, low-complexity, unauthenticated denial of service with no confidentiality or integrity impact - consistent with the CWE-401 memory leak described. CISA's SSVC framework aligns and tempers this: Exploitation=none (no observed or public exploitation), Automatable=yes (the unauthenticated network trigger can be scripted at scale), and Technical Impact=partial (service disruption, not full system control). The vulnerability is NOT in CISA KEV and no POC is referenced, so this is no public exploit identified at time of analysis. No EPSS score was provided, so exploitation probability cannot be quantified from the input. Net: this is a genuine patch-worthy issue for internet-exposed RD Gateway servers because the memory leak can be driven remotely without credentials and is automatable, but it is not an emergency - there is no evidence of active exploitation and the impact is limited to availability (service exhaustion/crash), not data theft or code execution. CONFLICT TO NOTE: the input Tag 'Authentication Bypass' contradicts both the description (a memory-leak DoS) and the CVSS impact triad (C:N/I:N/A:H); treat the tag as erroneous, not as evidence of an auth-bypass capability. |
| Exploit ScenarioDerived | An attacker locates an internet-facing Remote Desktop Gateway (commonly exposed on TCP 443 for remote access) and repeatedly sends connection requests that each cause the service to allocate memory that is never released. Over time the leaked memory exhausts available resources, degrading or crashing the RD Gateway Service and cutting off legitimate remote-access users. The CVSS AV:N/AC:L/PR:N/UI:N vector confirms this needs only network reach with no authentication, credentials, or user interaction; no public exploit code is currently identified. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Unauthenticated network traffic against the Remote Desktop Gateway (RD Gateway) role service on unpatched Windows Server builds causes a memory leak that is never released, progressively exhausting server memory until the gateway can no longer broker remote desktop sessions (CWE-401, CVSS 7.5, availability-only). Only hosts where the RD Gateway role service is installed, running, and reachable over the network are affected - typically internet-facing servers listening on TCP 443 - while servers without that role are not in scope. CISA's SSVC assessment records Exploitation: none and Technical Impact: partial, with Automatable: yes, and no public exploit has been identified at time of analysis; a vendor patch is available, so exposure is bounded to the enumerated pre-patch build ranges.
RemediationAI
Apply the vendor-released fixes from Microsoft: update Windows Server 2012 to 6.2.9200.26434, Windows Server 2012 R2 to 6.3.9600.23470, Windows Server 2016 (and Windows 10 1607) to 10.0.14393.9612, Windows Server 2019 (and Windows 10 1809) to 10.0.17763.9376, Windows Server 2022 to 10.0.20348.5761, and Windows Server 2025 to 10.0.26100.33650, per the MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-70033. Prioritize internet-facing RD Gateway hosts, since the pre-authentication, network-reachable nature of the leak means an exposed gateway can be driven into memory exhaustion without credentials; apply the update in a maintenance window because the RD Gateway service restarts and active RDP sessions brokered through it will drop. If patching cannot be performed immediately, the highest-value control is reducing reachability: place the RD Gateway behind a VPN or an allow-listed source-IP/geo restriction rather than exposing TCP 443 (and UDP 3391) directly to the internet, accepting the trade-off that legitimate mobile and remote users lose direct connectivity and must connect through the restricted path. Because no configuration switch is documented to disable the leak, operational mitigations should be treated as temporary: monitor gateway memory consumption and process growth and restart the RD Gateway service (or the host) before exhaustion to shed leaked memory - this only resets the leak and disconnects active sessions, so it must be repeated for as long as the system is unpatched. Where the role is not required, uninstalling the RD Gateway role service removes the attack surface entirely, and segmenting gateways from backend session hosts limits the blast radius to the gateway itself. There is no vendor-released patch gap to compensate for here; the update is available, and residual risk is confined to hosts that remain unpatched within the listed build ranges.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 13 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The underlying issue is CWE-401, Missing Release of Memory after Effective Lifetime - a classic memory leak in which the RD Gateway service allocates buffers or session objects per request and fails to free them after their effective lifetime, so consumption grows monotonically with request volume rather than returning to a baseline. RD Gateway is an optional Windows Server role service that publishes internal RDP endpoints to external clients using RDP over HTTPS (typically TCP 443, with UDP 3391 for the RDP-UDP transport when enabled), which is why the CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H is authenticated-free and network-reachable: an attacker needs no credentials, no user interaction, and no pre-existing session, only the ability to send requests to the gateway endpoint. The result is cumulative resource exhaustion rather than instantaneous corruption - no confidentiality or integrity impact, no code execution, and Scope: Unchanged - so the practical effect is degraded or refused service once memory pressure causes the service or host to become unresponsive. The associated tagging as an authentication bypass is consistent with the PR:N vector in that the leak can be induced before any authentication completes, and because SSVC marks the issue Automatable: yes, a scripted, repeated request pattern is sufficient, which raises the risk of sustained availability loss on internet-facing gateways. Note that the enumerated Windows 10 1607 and 1809 entries reflect shared servicing branches rather than the presence of the RD Gateway server role in client SKUs; the practical risk concentrates on Windows Server hosts explicitly configured with the role.
Know when Windows 10 1607 gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Remote unauthenticated memory-leak DoS needing no interaction gives AV:N/AC:L/PR:N/UI:N; impact is availability-only (A:H) with no confidentiality or integrity effect.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Missing release of memory after effective lifetime in Remote Desktop Gateway Service allows an unauthorized attacker to deny service over a network.
Executive ViewAI
An unauthenticated network-based memory exhaustion flaw in the Windows Server Remote Desktop Gateway role allows any internet-reachable server running that role to be gradually drained of memory until it stops brokering remote desktop sessions. Because RD Gateway is typically the internet-facing entry point for remote workforce access, the organizations most exposed are those relying on it for remote connectivity rather than those without the role deployed. Leadership should care because sustained loss of the gateway can disrupt remote work and administrative access for entire user populations, even though no data confidentiality or integrity risk is involved and no public exploit has been identified at time of analysis.
Apply vendor patch. Where patching is delayed, mitigate by limiting network reachability to RD Gateway endpoints (restrict TCP 443 to known source ranges, place behind VPN or WAF where feasible), enable automatic service recovery and scheduled service restarts to release leaked memory, and monitor server memory and RD Gateway session-brokering health for early signs of exhaustion.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
More in Windows 10 1607
View allWindows MSHTML component contains a remote code execution vulnerability that allows attackers to craft malicious ActiveX
<p>A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged fi
Windows MSDT (Microsoft Support Diagnostic Tool) allows remote code execution when called via the ms-msdt URL protocol f
The SMBv1 server in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows
The Windows VBScript engine contains a remote code execution vulnerability in object handling that allows full system co
Windows Print Spooler Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no auth
The Win32k kernel-mode driver in Windows Vista through Windows Server 2016 allows local privilege escalation, exploited
Windows Search Remote Code Execution Vulnerability. Rated high severity (CVSS 7.5), this vulnerability is remotely explo
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
Windows Kernel contains a TOCTOU race condition vulnerability allowing local privilege escalation, exploited by the OilR
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in
EUVD-2026-99139
GHSA-x4f6-7rhv-jqw4
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB