CVE-2025-59230: Microsoft Windows Improper Access Control Vulnerability

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

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

Description quoted from the CVE record (assigned by microsoft, published 2025-10-14).

Weakness: CWE-284: Improper Access Control

How it can be exploited

Exploitable with local access with low attack complexity needing low privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C

CISA assessment (SSVC): CISA assesses exploitation as active. Automatable: no. Technical impact: total.

On CISA KEV since
2025-10-14
US federal deadline
2025-11-04
Ransomware use
Not known

Public exploit evidence (Exploit Observer)

Also known as: BDU:2025-12964, CNNVD-202510-1812, EUVD-2025-34258, GHSA-8cmf-rx89-f229

Exploit Observer has no public exploit code that names this CVE or one of its aliases.

Research and write-ups (1)

Vulnerability databases and vendor advisories (10)

Catalogue entries, not exploit evidence.

56 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.

VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.

Live scores

EPSS
0.027
some chance of attack soon
VEDAS
0.744
some exploit evidence
On CISA KEV
Yes, since 2025-10-14
Detection rule
Out of scope (local)
EPSS (chance of attack)
10No cve-scores data 2026-02-22 to 2026-08-08no data0.1CVE-2025-59230 EPSS over time2025-112026-11-01
VEDAS (exploit evidence)
10No cve-scores data 2026-02-22 to 2026-08-08no data0.9CVE-2025-59230 VEDAS over time2025-112026-11-01

Thin horizontal line: the “likely” (EPSS 0.10) or “strong” (VEDAS 0.90) threshold. Shaded “no data” areas are periods when cve-scores did not publish.

Who is affected

ProductAffectedNot affected
Microsoft Windows 10 Version 1507from 10.0.10240.0 before 10.0.10240.21161Not stated
Microsoft Windows 10 Version 1607from 10.0.14393.0 before 10.0.14393.8519Not stated
Microsoft Windows 10 Version 1809from 10.0.17763.0 before 10.0.17763.7919Not stated
Microsoft Windows 10 Version 21H2from 10.0.19044.0 before 10.0.19044.6456Not stated
Microsoft Windows 10 Version 22H2from 10.0.19045.0 before 10.0.19045.6456Not stated
Microsoft Windows 11 version 22H2from 10.0.22621.0 before 10.0.22621.6060Not stated
Microsoft Windows 11 version 22H3from 10.0.22631.0 before 10.0.22631.6060Not stated
Microsoft Windows 11 Version 23H2from 10.0.22631.0 before 10.0.22631.6060Not stated
Microsoft Windows 11 Version 24H2from 10.0.26100.0 before 10.0.26100.6899Not stated
Microsoft Windows 11 Version 25H2from 10.0.26200.0 before 10.0.26200.6899Not stated
Microsoft Windows Server 2008 R2 Service Pack 1from 6.1.7601.0 before 6.1.7601.27974Not stated
Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)from 6.1.7601.0 before 6.1.7601.27974Not stated
Microsoft Windows Server 2008 Service Pack 2from 6.0.6003.0 before 6.0.6003.23571Not stated
Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)from 6.0.6003.0 before 6.0.6003.23571Not stated
Microsoft Windows Server 2012from 6.2.9200.0 before 6.2.9200.25722Not stated
Microsoft Windows Server 2012 (Server Core installation)from 6.2.9200.0 before 6.2.9200.25722Not stated
Microsoft Windows Server 2012 R2from 6.3.9600.0 before 6.3.9600.22824Not stated
Microsoft Windows Server 2012 R2 (Server Core installation)from 6.3.9600.0 before 6.3.9600.22824Not stated
Microsoft Windows Server 2016from 10.0.14393.0 before 10.0.14393.8519Not stated
Microsoft Windows Server 2016 (Server Core installation)from 10.0.14393.0 before 10.0.14393.8519Not stated

6 more products are listed in the CVE record.

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

Exploit Observer also maps it to: microsoft windows_10_1507, microsoft windows_10_1607, microsoft windows_10_1809, microsoft windows_10_21h2, microsoft windows_10_22h2, microsoft windows_11_22h2, microsoft windows_11_23h2, microsoft windows_11_24h2, microsoft windows_11_25h2, microsoft windows_server_2008.

How to fix it

Fixed versions stated in the CVE record: 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, 6.1.7601.27974, 6.0.6003.23571, 6.2.9200.25722 and others.

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.

Vendor guidance:

How to detect it

This bug needs local access to exploit. VEDAS signatures cover remotely exploitable bugs for now, so there is no network rule or remote check for it. Patch it and watch your endpoint telemetry for unusual local activity.

References

Vendor advisories and patches

Government sources

Other references

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, CISA KEV, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.