Windows Remote Desktop Services Remote Code Execution Vulnerability
Noroxi assessment
Priority: Monitor (action score 36/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 12.6% (FIRST EPSS); higher than 96.1% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Windows Server 2012 6.2.9200.25423; Windows Server 2012 (Server Core installation) 6.2.9200.25423; Windows Server 2012 R2 6.3.9600.22523.
Low priority for now. Upgrade to Windows Server 2012 6.2.9200.25423; Windows Server 2012 (Server Core installation) 6.2.9200.25423; Windows Server 2012 R2 6.3.9600.22523 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Use after free in Remote Desktop Gateway Service allows an unauthorized attacker to execute code over a network.
- Published
- Apr 8, 2025
- Updated
- Aug 10, 2026
- EPSS
- 12.6% · 96th percentile
- CWE
- CWE-416
Report tools
Action score
36
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 4 / 30 · 12.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · microsoft
- 8.1
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| microsoft | windows server 2012 | cpe:2.3:o:microsoft:windows_server_2012 |
| microsoft | windows server 2016 | cpe:2.3:o:microsoft:windows_server_2016 |
| microsoft | windows server 2019 | cpe:2.3:o:microsoft:windows_server_2019 |
| microsoft | windows server 2022 | cpe:2.3:o:microsoft:windows_server_2022 |
| microsoft | windows server 2022 23h2 | cpe:2.3:o:microsoft:windows_server_2022_23h2 |
| microsoft | windows server 2025 | cpe:2.3:o:microsoft:windows_server_2025 |
Using windows server 2012? Add it to your stack and be the first to know about CVEs like this one. (Windows Server, Active Directory)
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- microsoft windows server 2012all versions
- microsoft windows server 2012r2
- microsoft windows server 2016before 10.0.14393.7969
- microsoft windows server 2019before 10.0.17763.7136
- microsoft windows server 2022before 10.0.20348.3453
- microsoft windows server 2022 23h2before 10.0.25398.1551
- microsoft windows server 2025before 10.0.26100.3775
Versions reported by the vendor
Affected version ranges reported by the assigning authority (microsoft). Independent of NVD's CPE analysis and usually ahead of it.
Microsoft Windows Server 2012
- 6.2.9200.0 and later · before 6.2.9200.25423affected
Microsoft Windows Server 2012 (Server Core installation)
- 6.2.9200.0 and later · before 6.2.9200.25423affected
Microsoft Windows Server 2012 R2
- 6.3.9600.0 and later · before 6.3.9600.22523affected
Microsoft Windows Server 2012 R2 (Server Core installation)
- 6.3.9600.0 and later · before 6.3.9600.22523affected
Microsoft Windows Server 2016
- 10.0.14393.0 and later · before 10.0.14393.7969affected
Microsoft Windows Server 2016 (Server Core installation)
- 10.0.14393.0 and later · before 10.0.14393.7969affected
Microsoft Windows Server 2019
- 10.0.17763.0 and later · before 10.0.17763.7136affected
Microsoft Windows Server 2019 (Server Core installation)
- 10.0.17763.0 and later · before 10.0.17763.7136affected
Microsoft Windows Server 2022
- 10.0.20348.0 and later · before 10.0.20348.3453affected
Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)
- 10.0.25398.0 and later · before 10.0.25398.1551affected
Microsoft Windows Server 2025
- 10.0.26100.0 and later · before 10.0.26100.3775affected
Microsoft Windows Server 2025 (Server Core installation)
- 10.0.26100.0 and later · before 10.0.26100.3775affected
Same product
microsoft: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-59287Windows Server Update Service (WSUS) Remote Code Execution VulnerabilityKEV99Now
- CVE-2023-24941Windows Network File System Remote Code Execution Vulnerability67This week
- CVE-2020-0609A remote code execution vulnerability exists in Windows Remote Desktop Gateway (RD Gateway) when an unauthenticated attacker connects to the62This week
- CVE-2022-30136Windows Network File System Remote Code Execution Vulnerability61This week
- CVE-2020-0610A remote code execution vulnerability exists in Windows Remote Desktop Gateway (RD Gateway) when an unauthenticated attacker connects to the59Plan
- CVE-2013-3182The Windows NAT Driver (aka winnat) service in Microsoft Windows Server 2012 does not properly validate memory addresses during the processi59Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Windows Server 2012 | 6.2.9200.25423 · KB5055581 | Microsoft (MSRC) |
| Windows Server 2012 (Server Core installation) | 6.2.9200.25423 · KB5055581 | Microsoft (MSRC) |
| Windows Server 2012 R2 | 6.3.9600.22523 · KB5055557 | Microsoft (MSRC) |
| Windows Server 2012 R2 (Server Core installation) | 6.3.9600.22523 · KB5055557 | Microsoft (MSRC) |
| Windows Server 2016 | 10.0.14393.7969 · KB5055521 | Microsoft (MSRC) |
| Windows Server 2016 (Server Core installation) | 10.0.14393.7969 · KB5055521 | Microsoft (MSRC) |
| Windows Server 2019 | 10.0.17763.7136 · KB5055519 | Microsoft (MSRC) |
| Windows Server 2019 (Server Core installation) | 10.0.17763.7136 · KB5055519 | Microsoft (MSRC) |
| Windows Server 2022 | 10.0.20348.3453 · KB5055526 | Microsoft (MSRC) |
| Windows Server 2022 (Server Core installation) | 10.0.20348.3453 · KB5055526 | Microsoft (MSRC) |
| Windows Server 2022, 23H2 Edition (Server Core installation) | 10.0.25398.1551 · KB5055527 | Microsoft (MSRC) |
| Windows Server 2025 | 10.0.26100.3775 · KB5055523 | Microsoft (MSRC) |
| Windows Server 2025 (Server Core installation) | 10.0.26100.3775 · KB5055523 | Microsoft (MSRC) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×2
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2025-09-01 |
| Proof-of-concept repository on GitHub | stars:0 | 2025-09-03 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+145 d
- TodayOct 13, 2026+553 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-3307163 days apartWindows KDC Proxy Service (KPSSVC) Remote Code Execution Vulnerability39Monitor
- CVE-2026-69595518 days apartWindows Services for NFS ONCRPC XDR Driver Remote Code Execution Vulnerability39Monitor
- CVE-2026-78445518 days apartWindows Services for NFS ONCRPC XDR Driver Remote Code Execution Vulnerability39Monitor
- CVE-2026-69712518 days apartWindows Key Distribution Center Remote Code Execution Vulnerability35Monitor
- CVE-2025-4973591 days apartWindows KDC Proxy Service (KPSSVC) Remote Code Execution Vulnerability32Monitor
- CVE-2024-49128118 days apartWindows Remote Desktop Services Remote Code Execution Vulnerability32Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);Fixed
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.