CriticalCVE-2025-59230

    Windows Remote Access Connection Manager Elevation of Privilege Vulnerability (CVE-2025-59230)

    Published In CISA KEV since Sources: pwn.watch, CVE.org, Msrc Update Guide

    What is affected, what to do

    Improper access control in Windows Remote Access Connection Manager allows an authorized attacker to elevate privileges locally.

    The vulnerability is being actively exploited; treat it as a priority. Update Microsoft Windows 10 Version 1507 to version 10.0.10240.21161, Microsoft Windows 10 Version 1607 to version 10.0.14393.8519, Microsoft Windows 10 Version 1809 to version 10.0.17763.7919. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Microsoft Windows 10 Version 1507 lt 10.0.10240.0..10.0.10240.21161
    • Microsoft Windows 10 Version 1607 lt 10.0.14393.0..10.0.14393.8519
    • Microsoft Windows 10 Version 1809 lt 10.0.17763.0..10.0.17763.7919
    • Microsoft Windows 10 Version 21H2 lt 10.0.19044.0..10.0.19044.6456
    • Microsoft Windows 10 Version 22H2 lt 10.0.19045.0..10.0.19045.6456
    • Microsoft Windows 11 version 22H2 lt 10.0.22621.0..10.0.22621.6060
    • Microsoft Windows 11 version 22H3 lt 10.0.22631.0..10.0.22631.6060
    • Microsoft Windows 11 Version 23H2 lt 10.0.22631.0..10.0.22631.6060
    • Microsoft Windows 11 Version 24H2 lt 10.0.26100.0..10.0.26100.6899
    • Microsoft Windows 11 Version 25H2 lt 10.0.26200.0..10.0.26200.6899
    • Microsoft Windows Server 2008 R2 Service Pack 1 lt 6.1.7601.0..6.1.7601.27974
    • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation) lt 6.1.7601.0..6.1.7601.27974
    • Microsoft Windows Server 2008 Service Pack 2 lt 6.0.6003.0..6.0.6003.23571
    • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation) lt 6.0.6003.0..6.0.6003.23571
    • Microsoft Windows Server 2012 lt 6.2.9200.0..6.2.9200.25722
    • Microsoft Windows Server 2012 (Server Core installation) lt 6.2.9200.0..6.2.9200.25722
    • Microsoft Windows Server 2012 R2 lt 6.3.9600.0..6.3.9600.22824
    • Microsoft Windows Server 2012 R2 (Server Core installation) lt 6.3.9600.0..6.3.9600.22824
    • Microsoft Windows Server 2016 lt 10.0.14393.0..10.0.14393.8519
    • Microsoft Windows Server 2016 (Server Core installation) lt 10.0.14393.0..10.0.14393.8519
    • Microsoft Windows Server 2019 lt 10.0.17763.0..10.0.17763.7919
    • Microsoft Windows Server 2019 (Server Core installation) lt 10.0.17763.0..10.0.17763.7919
    • Microsoft Windows Server 2022 lt 10.0.20348.0..10.0.20348.4294
    • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation) lt 10.0.25398.0..10.0.25398.1913
    • Microsoft Windows Server 2025 lt 10.0.26100.0..10.0.26100.6899
    • Microsoft Windows Server 2025 (Server Core installation) lt 10.0.26100.0..10.0.26100.6899
    Fixed in
    • Microsoft Windows 10 Version 1507 10.0.10240.21161
    • Microsoft Windows 10 Version 1607 10.0.14393.8519
    • Microsoft Windows 10 Version 1809 10.0.17763.7919
    • Microsoft Windows 10 Version 21H2 10.0.19044.6456
    • Microsoft Windows 10 Version 22H2 10.0.19045.6456
    • Microsoft Windows 11 version 22H2 10.0.22621.6060
    • Microsoft Windows 11 version 22H3 10.0.22631.6060
    • Microsoft Windows 11 Version 23H2 10.0.22631.6060
    • Microsoft Windows 11 Version 24H2 10.0.26100.6899
    • Microsoft Windows 11 Version 25H2 10.0.26200.6899
    • Microsoft Windows Server 2008 R2 Service Pack 1 6.1.7601.27974
    • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation) 6.1.7601.27974
    • Microsoft Windows Server 2008 Service Pack 2 6.0.6003.23571
    • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation) 6.0.6003.23571
    • Microsoft Windows Server 2012 6.2.9200.25722
    • Microsoft Windows Server 2012 (Server Core installation) 6.2.9200.25722
    • Microsoft Windows Server 2012 R2 6.3.9600.22824
    • Microsoft Windows Server 2012 R2 (Server Core installation) 6.3.9600.22824
    • Microsoft Windows Server 2016 10.0.14393.8519
    • Microsoft Windows Server 2016 (Server Core installation) 10.0.14393.8519
    • Microsoft Windows Server 2019 10.0.17763.7919
    • Microsoft Windows Server 2019 (Server Core installation) 10.0.17763.7919
    • Microsoft Windows Server 2022 10.0.20348.4294
    • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation) 10.0.25398.1913
    • Microsoft Windows Server 2025 10.0.26100.6899
    • Microsoft Windows Server 2025 (Server Core installation) 10.0.26100.6899

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    7.8

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    7.8

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: pwn.watch, CVE.org, Msrc Update Guide

    2.7 %

    EPSS score

    Moderate — model estimates 1-10% exploitation likelihood.

    Source: FIRST EPSS, percentile 85.7

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    209.13 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploitedSource: VulnCheck KEV (opens in a new tab) How we classify
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    7.8 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    7.8
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    2.7 %
    Moderate — model estimates 1-10% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    85.7
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CISA assessment (SSVC)
    Exploitation: active · not automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 15 October 2025
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-284

    Response and mitigation

    Why act now?

    Prioritisation rationale

    The flaw requires prior local code execution with low privileges. Once that foothold exists, it is low-complexity, needs no user interaction and yields full host compromise. That makes it the textbook second stage after phishing, infostealers or abused VPN/RDP accounts, and its KEV listing on patch day points to targeted use before the fix shipped. Exploitation likelihood is clearly above average but not in the top tier, and CISA reports no known ransomware use. Treat it as high priority on an accelerated cycle (within days), and as critical for multi-user and admin systems or organisations with heavy phishing pressure. Internet-exposure-only scoring will underrate it.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Deploy Microsoft's October 2025 security update. Target builds (Build.UBR): Windows 10 1507 → 10.0.10240.21161, 1607 → 10.0.14393.8519, 1809 → 10.0.17763.7919, 21H2 → 10.0.19044.6456, 22H2 → 10.0.19045.6456; Windows 11 22H2 → 10.0.22621.6060, 23H2 → 10.0.22631.6060. Look up the per-build KB number in the Microsoft Security Update Guide entry for CVE-2025-59230. Windows Server builds are not listed in this context, so verify server exposure in the vendor advisory.
      • Inventory patch state. Pull the build via Intune, SCCM, Defender TVM or a script: $k=Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion'; "$($k.CurrentBuild).$($k.UBR)". Flag every host below the target build as open.
      • Patch multi-user and admin endpoints first. This covers RDS/Citrix hosts, VDI, jump hosts, PAWs, and admin and helpdesk workstations. On these systems a local privilege escalation leads straight to privileged credentials.
      • Treat hosts with recent initial-access alerts as suspect. Any host that has raised phishing payload, infostealer or loader alerts in recent weeks should be considered potentially SYSTEM-compromised. Isolate it via EDR and reset cached credentials for accounts that logged on there.
      • Identify unsupported Windows 10 builds. Windows 10 22H2 without an ESU contract receives no further fixes after October 2025. Escalate these hosts for migration or ESU procurement.

    2. Runbook step 2

      Mitigation layers

      • Configuration change: Where neither the built-in Windows VPN client, Always On VPN nor dial-up is needed (servers, kiosks, OT HMIs), disable the RasMan service: sc.exe config RasMan start= disabled and Stop-Service RasMan -Force. Check dependencies first, because the RemoteAccess service requires RasMan and some third-party VPN clients may break.
      • Endpoint hardening: Set ASR rules to block mode, notably "Block credential stealing from LSASS" and "Block executable files unless they meet prevalence, age or trusted list criteria". Also enable LSA protection (RunAsPPL) and Credential Guard. This limits what an attacker can do with SYSTEM rights.
      • Application control: Apply WDAC or AppLocker rules to user-writable paths (%TEMP%, %APPDATA%, Downloads, C:\Users\Public). Exploit binaries are typically launched from these paths.
      • IAM/least privilege: Remove local admin rights and enforce Windows LAPS for unique local admin passwords. Keep privileged domain accounts off standard clients (tiering model, "Deny log on locally" for Tier 0 on Tier 2).
      • Network segmentation: Restrict lateral movement after escalation. Block client-to-client SMB (445), RPC (135) and WinRM (5985/5986) via a Windows Firewall GPO, and allow these protocols only from dedicated admin subnets.

    3. Runbook step 3

      Detection rules

      • Sysmon EID 1 / Security 4688 – unusual children of the RasMan service host: svchost.exe with -s RasMan in its command line spawning cmd.exe, powershell.exe, rundll32.exe or unsigned binaries. KQL: DeviceProcessEvents | where InitiatingProcessFileName =~ "svchost.exe" and InitiatingProcessCommandLine has "RasMan" | where FileName in~ ("cmd.exe","powershell.exe","pwsh.exe","rundll32.exe","regsvr32.exe")
      • Integrity jump in process ancestry: A System-integrity process whose tree traces back to a medium-integrity user session (EDR ancestry), especially when its image path is under \Users\. Sigma shape: IntegrityLevel: System + Image|contains: '\Users\' + User|endswith: 'SYSTEM'.
      • Sysmon EID 12/13 – registry tampering: Writes to HKLM\SYSTEM\CurrentControlSet\Services\RasMan\* or HKLM\SOFTWARE\Microsoft\RasMan\* by any process other than svchost.exe, services.exe or TrustedInstaller.exe.
      • Post-escalation activity: LSASS access (Sysmon EID 10, TargetImage lsass.exe, GrantedAccess 0x1010/0x1410), new service installs (System 7045, Security 4697) and local Administrators group changes (4732), each shortly after execution from a user path.
      • System 7036/7040: Unexpected start/stop cycles or start-type changes of RasMan on hosts that do not use VPN.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    Improper access control in Windows Remote Access Connection Manager allows an authorized attacker to elevate privileges locally.

    Source: pwn.watch, NVD (NIST), CISA KEV Catalog, CVE.org (MITRE), Microsoft Security Update Guide, cvelistv5

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    MicrosoftWindows 10 Version 1507
    • 10.0.10240.0 – < 10.0.10240.21161
    • 10.0.10240.21161
    MicrosoftWindows 10 Version 1607
    • 10.0.14393.0 – < 10.0.14393.8519
    • 10.0.14393.8519
    MicrosoftWindows 10 Version 1809
    • 10.0.17763.0 – < 10.0.17763.7919
    • 10.0.17763.7919
    MicrosoftWindows 10 Version 21H2
    • 10.0.19044.0 – < 10.0.19044.6456
    • 10.0.19044.6456
    MicrosoftWindows 10 Version 22H2
    • 10.0.19045.0 – < 10.0.19045.6456
    • 10.0.19045.6456
    MicrosoftWindows 11 version 22H2
    • 10.0.22621.0 – < 10.0.22621.6060
    • 10.0.22621.6060
    MicrosoftWindows 11 version 22H3
    • 10.0.22631.0 – < 10.0.22631.6060
    • 10.0.22631.6060
    MicrosoftWindows 11 Version 23H2
    • 10.0.22631.0 – < 10.0.22631.6060
    • 10.0.22631.6060
    MicrosoftWindows 11 Version 24H2
    • 10.0.26100.0 – < 10.0.26100.6899
    • 10.0.26100.6899
    MicrosoftWindows 11 Version 25H2
    • 10.0.26200.0 – < 10.0.26200.6899
    • 10.0.26200.6899
    MicrosoftWindows Server 2008 R2 Service Pack 1
    • 6.1.7601.0 – < 6.1.7601.27974
    • 6.1.7601.27974
    MicrosoftWindows Server 2008 R2 Service Pack 1 (Server Core installation)
    • 6.1.7601.0 – < 6.1.7601.27974
    • 6.1.7601.27974
    MicrosoftWindows Server 2008 Service Pack 2
    • 6.0.6003.0 – < 6.0.6003.23571
    • 6.0.6003.23571
    MicrosoftWindows Server 2008 Service Pack 2 (Server Core installation)
    • 6.0.6003.0 – < 6.0.6003.23571
    • 6.0.6003.23571
    MicrosoftWindows Server 2012
    • 6.2.9200.0 – < 6.2.9200.25722
    • 6.2.9200.25722
    MicrosoftWindows Server 2012 (Server Core installation)
    • 6.2.9200.0 – < 6.2.9200.25722
    • 6.2.9200.25722
    MicrosoftWindows Server 2012 R2
    • 6.3.9600.0 – < 6.3.9600.22824
    • 6.3.9600.22824
    MicrosoftWindows Server 2012 R2 (Server Core installation)
    • 6.3.9600.0 – < 6.3.9600.22824
    • 6.3.9600.22824
    MicrosoftWindows Server 2016
    • 10.0.14393.0 – < 10.0.14393.8519
    • 10.0.14393.8519
    MicrosoftWindows Server 2016 (Server Core installation)
    • 10.0.14393.0 – < 10.0.14393.8519
    • 10.0.14393.8519
    MicrosoftWindows Server 2019
    • 10.0.17763.0 – < 10.0.17763.7919
    • 10.0.17763.7919
    MicrosoftWindows Server 2019 (Server Core installation)
    • 10.0.17763.0 – < 10.0.17763.7919
    • 10.0.17763.7919
    MicrosoftWindows Server 2022
    • 10.0.20348.0 – < 10.0.20348.4294
    • 10.0.20348.4294
    MicrosoftWindows Server 2022, 23H2 Edition (Server Core installation)
    • 10.0.25398.0 – < 10.0.25398.1913
    • 10.0.25398.1913
    MicrosoftWindows Server 2025
    • 10.0.26100.0 – < 10.0.26100.6899
    • 10.0.26100.6899
    MicrosoftWindows Server 2025 (Server Core installation)
    • 10.0.26100.0 – < 10.0.26100.6899
    • 10.0.26100.6899

    Vendors and products

    Affected operating systems

    Affected operating systems
    Windowsmicrosoftwindows_10_1507—
    Windowsmicrosoftwindows_10_1607—
    Windowsmicrosoftwindows_10_1809—
    Windowsmicrosoftwindows_10_21h2—
    Windowsmicrosoftwindows_10_22h2—
    Windowsmicrosoftwindows_11_22h2—
    Windowsmicrosoftwindows_11_23h2—
    Windowsmicrosoftwindows_11_24h2—
    Windowsmicrosoftwindows_11_25h2—
    Windowsmicrosoftwindows_server_2008r2
    Windowsmicrosoftwindows_server_2008—
    Windowsmicrosoftwindows_server_2012r2
    Windowsmicrosoftwindows_server_2012—
    Windowsmicrosoftwindows_server_2016—
    Windowsmicrosoftwindows_server_2019—
    Windowsmicrosoftwindows_server_2022—
    Windowsmicrosoftwindows_server_2022_23h2—
    Windowsmicrosoftwindows_server_2025—

    Weakness classes (CWE)

    • CWE-284Improper Access Control

      Pillar

      The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

      Entry at MITRE CWE-284

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited

    References & sources

    • Microsoft Security Update GuideWindows Remote Access Connection Manager Elevation of Privilege VulnerabilityVendor advisory, Patch, Vendor advisory
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2025-59230government-resource, US government resource
    • vicarius.iovsociety/posts/cve-2025-59230-detection-script-elevation-of-pri…Third-party advisory
    • vicarius.iovsociety/posts/cve-2025-59230-mitigation-script-elevation-of-pr…Mitigation, Third-party advisory
    • pwn.watchpwn.watch: Microsoft Windows: 2 exploited vulnerabilities (CVE-2025-24990, CVE-2025-59230)pwn-watch
    • Microsoft Security Update GuideMicrosoft advisory: Microsoft Windowspwn-watch
    • Microsoft Security Update GuideMicrosoft advisory: Microsoft Windowspwn-watch
    • NVD (NIST)NVD: CVE-2025-24990pwn-watch
    • NVD (NIST)NVD: CVE-2025-59230pwn-watch
    • cisa.govCISA Known Exploited Vulnerabilities Catalogpwn-watch
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2025-59230
    <a href="https://intel.neosec.eu/en/cve/CVE-2025-59230"><img src="https://intel.neosec.eu/badge/cve/CVE-2025-59230.svg?lang=en" alt="CVE-2025-59230 – NEOSEC Intel" height="20"></a>