Security readout for executives and security teams
Plain-English summary
This Microsoft Windows RD Gateway issue can cause a denial of service, meaning affected systems may become unavailable. The provided sources rate it medium severity with high availability impact, but no confidentiality or integrity impact. It is not listed as CISA KEV, and the bundle provides no evidence of active exploitation.
Executive priority
Handle through normal monthly patch governance, with higher priority for RD Gateway systems supporting business remote access. The main business risk is service disruption, not data theft based on the provided sources.
Technical view
CVE-2025-21278 is a CWE-362 race condition in Windows Remote Desktop Gateway. CVSS 3.1 is 6.2 with local attack vector, low complexity, no privileges, no user interaction, unchanged scope, and high availability impact only. Microsoft lists updates as available for affected Windows client and server versions.
Likely exposure
Exposure is most relevant to organizations running the listed Microsoft Windows versions, especially systems where RD Gateway is present or relied on for remote access. Validate actual exposure through asset inventory, installed roles, and patch status rather than assuming every listed Windows host is exploitable.
Exploitation context
The source bundle marks KEV as false and CVSS exploit maturity as unproven. No cited source states active exploitation or provides public exploit details. Treat this as an availability risk requiring patch management attention, not as a confirmed in-the-wild compromise signal.
Researcher notes
The key technical clue is CWE-362, indicating a race condition. The CVSS vector limits impact to availability and records local attack vector. The public bundle does not include root-cause detail, crash conditions, exploit primitives, or named mitigations beyond Microsoft updates.
Mitigation direction
Apply the Microsoft security update for affected Windows versions.
Prioritize RD Gateway servers and critical remote-access infrastructure.
Use MSRC guidance for exact affected builds and update applicability.
If patching is delayed, check Microsoft guidance for supported compensating controls.
Validation and detection
Inventory Windows hosts matching the affected versions listed by Microsoft.
Identify systems with RD Gateway installed, enabled, or operationally required.
Confirm the relevant Microsoft security update is installed.
Track unresolved RD Gateway hosts as availability-risk exceptions until remediated.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-362: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-362 · source CWE mapping
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.