Skip to content
Server Security Center
KEVhigh7.8

CVE-2025-59230: Microsoft Windows Improper Access Control

Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2025-10-14.

CVSS v3.1 (CVE record)
7.8
high
EPSS (exploit probability, 30 days)
3.0%
higher than 87.6% of all CVEs
Added to CISA KEV
2025-10-14
US federal due date 2025-11-04
Automatable (CISA SSVC)
no
technical impact: total

CVE-2025-59230 explained

CVE-2025-59230 is an improper access control flaw (CWE-284) in Windows Remote Access Connection Manager. An authorized local attacker can use it to elevate privileges on the affected system. CISA lists it as known to be exploited, so affected Windows clients and servers should be patched with priority.

Impact

An attacker who already has low-privileged local access can elevate privileges without user interaction. Confidentiality, integrity and availability impacts are all high. CISA rates the technical impact as total, meaning full control of the affected system. CISA rates it as not automatable, so it is unlikely to be exploited at scale without manual steps. It is in CISA's Known Exploited Vulnerabilities catalog. Known ransomware use is listed as unknown.

Who is affected

The CVE record lists Windows 10 versions 1507, 1607, 1809, 21H2 and 22H2. It also lists Windows 11 versions 22H2, 22H3, 23H2, 24H2 and 25H2, plus Windows Server 2008 R2 Service Pack 1, including Server Core. Fixed builds include 10.0.10240.21161, 10.0.14393.8519, 10.0.17763.7919, 10.0.19044.6456, 10.0.19045.6456, 10.0.22621.6060, 10.0.22631.6060, 10.0.26100.6899, 10.0.26200.6899 and 6.1.7601.27974. The page lists 14 further products.

Written with AI from the data on this page and checked against it automatically.

Official description

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

CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft Windows 10 Version 150732-bit, x64
    Affected
    • < 10.0.10240.21161
    Fixed in
    • 10.0.10240.21161
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.8519
    Fixed in
    • 10.0.14393.8519
  • Microsoft Windows 10 Version 180932-bit, x64
    Affected
    • < 10.0.17763.7919
    Fixed in
    • 10.0.17763.7919
  • Microsoft Windows 10 Version 21H232-bit, ARM64, x64
    Affected
    • < 10.0.19044.6456
    Fixed in
    • 10.0.19044.6456
  • Microsoft Windows 10 Version 22H232-bit, ARM64, x64
    Affected
    • < 10.0.19045.6456
    Fixed in
    • 10.0.19045.6456
  • Microsoft Windows 11 version 22H2ARM64, x64
    Affected
    • < 10.0.22621.6060
    Fixed in
    • 10.0.22621.6060
  • Microsoft Windows 11 version 22H3ARM64
    Affected
    • < 10.0.22631.6060
    Fixed in
    • 10.0.22631.6060
  • Microsoft Windows 11 Version 23H2x64
    Affected
    • < 10.0.22631.6060
    Fixed in
    • 10.0.22631.6060
  • Microsoft Windows 11 Version 24H2ARM64, x64
    Affected
    • < 10.0.26100.6899
    Fixed in
    • 10.0.26100.6899
  • Microsoft Windows 11 Version 25H2
    Affected
    • < 10.0.26200.6899
    Fixed in
    • 10.0.26200.6899
Show 16 more products
  • Microsoft Windows Server 2008 R2 Service Pack 1x64
    Affected
    • < 6.1.7601.27974
    Fixed in
    • 6.1.7601.27974
  • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64
    Affected
    • < 6.1.7601.27974
    Fixed in
    • 6.1.7601.27974
  • Microsoft Windows Server 2008 Service Pack 232-bit, x64
    Affected
    • < 6.0.6003.23571
    Fixed in
    • 6.0.6003.23571
  • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64
    Affected
    • < 6.0.6003.23571
    Fixed in
    • 6.0.6003.23571
  • Microsoft Windows Server 2012x64
    Affected
    • < 6.2.9200.25722
    Fixed in
    • 6.2.9200.25722
  • Microsoft Windows Server 2012 (Server Core installation)x64
    Affected
    • < 6.2.9200.25722
    Fixed in
    • 6.2.9200.25722
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.22824
    Fixed in
    • 6.3.9600.22824
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.22824
    Fixed in
    • 6.3.9600.22824
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.8519
    Fixed in
    • 10.0.14393.8519
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.8519
    Fixed in
    • 10.0.14393.8519
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.7919
    Fixed in
    • 10.0.17763.7919
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.7919
    Fixed in
    • 10.0.17763.7919
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.4294
    Fixed in
    • 10.0.20348.4294
  • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64
    Affected
    • < 10.0.25398.1913
    Fixed in
    • 10.0.25398.1913
  • Microsoft Windows Server 2025x64
    Affected
    • < 10.0.26100.6899
    Fixed in
    • 10.0.26100.6899
  • Microsoft Windows Server 2025 (Server Core installation)x64
    Affected
    • < 10.0.26100.6899
    Fixed in
    • 10.0.26100.6899

How to fix it

  • Update to the fixed version for your product:
    • 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
    Fixed versions for 20 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2025-59230
  • CISA's deadline for US federal agencies: 2025-11-04 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Install the Microsoft security update that brings each system to the fixed build listed for its Windows version, for example 10.0.26100.6899 for Windows 11 24H2.
  2. Check the vendor advisory for the further affected products listed on this page and patch them as well.
  3. Prioritize multi-user systems and servers, because the attacker needs local, low-privileged access.
  4. Limit local and interactive logon rights to trusted users and review accounts with local access.
  5. Check systems for signs of compromise, such as unexpected privilege changes or new administrative accounts.
  6. US federal agencies must follow CISA's required action by 2025-11-04.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-284 Improper Access Control

Questions about CVE-2025-59230

Is CVE-2025-59230 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-10-14. Whether it is used in ransomware campaigns is listed as unknown.
Can it be exploited remotely?
No. The attack vector is local. The attacker must already be authorized on the system with low privileges. No user interaction is needed.
Which build fixes Windows 10 22H2?
The CVE record lists 10.0.19045.6456 as the fixed build for Microsoft Windows 10 Version 22H2.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.