dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 4 Nov 2025.
Windows 10 1507Operating system · Microsoft

CVE-2025-59230

HIGH · 7.8 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 10.0.10240.21161 / 10.0.14393.8519 or later.
See remediation →
96/100
Remediation priority · Urgent
In the wild Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Improper access control in Windows Remote Access Connection Manager (RasMan service) allows a locally authenticated attacker to escalate privileges to SYSTEM level by exploiting insufficient authorization checks on the service or its associated resources.

MitigationApply the Microsoft security update addressing CVE-2025-59230. Until patched, limit local system access to trusted users only and monitor for anomalous interactions with the Remote Access Connection Manager service.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1507Operating system
Affected:< 10.0.10240.21161
Windows 10 1607Operating system
Affected:< 10.0.14393.8519
Windows 10 1809Operating system
Affected:< 10.0.17763.7919
Windows 10 21h2Operating system
Affected:< 10.0.19044.6456
Windows 10 22h2Operating system
Affected:< 10.0.19045.6456
Windows 11 22h2Operating system
Affected:< 10.0.22621.6060
Windows 11 23h2Operating system
Affected:<= 10.0.22631.6060
Windows 11 24h2Operating system
Affected:< 10.0.26100.6899

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Windows version and build number
    Open Command Prompt and run `systeminfo | findstr /C:"OS Version"` or check System Properties (winver) to get the full build number
    Affected if Build number is lower than the fixed versions for your Windows release (10.0.10240.21161 for 1507, 10.0.14393.8519 for 1607, 10.0.17763.7919 for 1809, 10.0.19044.6456 for 21h2, 10.0.19045.6456 for 22h2, 10.0.22621.6060 for 11 22h2, 10.0.22631.6060 for 11 23h2, or 10.0.26100.6899 for 11 24h2)
  2. Confirm Rasman service is present
    Open Services.msc and locate Remote Access Connection Manager (Rasman), or run `sc query Rasman` in Command Prompt
    Affected if The Rasman service exists on the system (the vulnerability affects this service)
  3. Check if security update is installed
    Run `wmic qfe list` or open Windows Update history to look for the CVE-2025-59230 security update
    Affected if The specific security update for this CVE is not listed as installed

Your system is affected if it runs a Windows version with a build number lower than the fixed version for your release AND the Rasman service is present AND the security update is not installed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.10240.21161 / 10.0.14393.8519 / 10.0.17763.7919 or later
Fixed in 10.0.10240.2116110.0.14393.851910.0.17763.7919
Interim mitigation

Apply the Microsoft security update addressing CVE-2025-59230. Until patched, limit local system access to trusted users only and monitor for anomalous interactions with the Remote Access Connection Manager service.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.21161+ | Windows 10 1607: 10.0.14393.8519+ | Windows 10 1809: 10.0.17763.7919+ | Windows 10 21h2: 10.0.19044.6456+ | Windows 10 22h2: 10.0.19045.6456+ | Windows 11 22h2: 10.0.22621.6060+ | Windows 11 23h2: 10.0.22631.7000+ | Windows 11 24h2: 10.0.26100.6899+

  1. Open Settings > Update & Security > Windows Update and check for available updates
  2. Install the latest Windows security update that addresses this vulnerability (KB reference: CVE-2025-59230)
  3. Restart the computer after the update is installed
  4. Verify the update was applied by checking Windows Update history or running winver to confirm the version matches or exceeds the fixed version for your build
Caveat Standard Windows cumulative updates typically have minimal breaking changes; ensure critical applications are tested after update deployment in enterprise environments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1507 Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59230 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59230 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data