Skip to main content
Mallory
HighExploited in the wildCISA KEVVulnerability

CVE-2025-59230: Windows Remote Access Connection Manager Local Privilege Escalation

Published Oct 14, 2025 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS2.7%86th percentile
CISA KEVYesAdded Oct 14, 2025
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2025-59230CWE-284 · Improper Access Control

CVE-2025-59230 is an improper access control vulnerability in Windows Remote Access Connection Manager (RasMan) that allows an authenticated local attacker to elevate privileges to SYSTEM. The vulnerability involves RPC endpoint registration: an attacker can impersonate RasMan by registering its trusted endpoint before the legitimate service starts, causing privileged clients to connect to an attacker-controlled process. This Endpoint Mapper poisoning technique can enable arbitrary code execution as SYSTEM. Exploitation was observed in the wild before Microsoft patched the vulnerability in October 2025.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation elevates an authenticated local attacker to SYSTEM and can enable arbitrary code execution with SYSTEM privileges, compromising the affected Windows host. The vulnerability is a local privilege-escalation flaw, not an independently established remote initial-access vulnerability.

Mitigation

If you can’t patch tonight, do this now.

Monitor RPC endpoint registration for unexpected registration of built-in interfaces and use Microsoft-Windows-RPC ETW telemetry to identify unknown processes receiving connections on those interfaces. These detection measures do not replace patching. No confirmed vulnerability-specific workaround is available.

Remediation

Patch, then assume compromise.

Install the applicable Microsoft Windows security updates released in October 2025, or subsequent updates that include the fix. Prioritize affected hosts because exploitation has been observed in the wild. Consult the Microsoft Security Update Guide for product-specific packages; exact fixed builds and KB identifiers are not available here.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows 10 1507operating_system
Microsoft CorporationWindows 10 1607operating_system
Microsoft CorporationWindows 10 1809operating_system
Microsoft CorporationWindows 10 21h2operating_system
Microsoft CorporationWindows 10 22h2operating_system
Microsoft CorporationWindows 11 22h2operating_system
Microsoft CorporationWindows 11 23h2operating_system
Microsoft CorporationWindows 11 24h2operating_system
Microsoft CorporationWindows 11 25h2operating_system
Microsoft CorporationWindows Server 2008operating_system
Microsoft CorporationWindows Server 2008 R2operating_system
Microsoft CorporationWindows Server 2008 Sp2operating_system
Microsoft CorporationWindows Server 2012operating_system
Microsoft CorporationWindows Server 2012 R2operating_system
Microsoft CorporationWindows Server 2016operating_system
Microsoft CorporationWindows Server 2019operating_system
Microsoft CorporationWindows Server 2022operating_system
Microsoft CorporationWindows Server 2022 23h2operating_system
Microsoft CorporationWindows Server 2025operating_system
Microsoft CorporationWindows Server 23h2operating_system
FAQ

Frequently asked questions

Is CVE-2025-59230 exploited in the wild?
Yes. As of Oct 10, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Oct 14, 2025.
Is there a public exploit for CVE-2025-59230?
As of Oct 10, 2026, Mallory has found no public exploit for CVE-2025-59230.
Is there a patch for CVE-2025-59230?
Install the applicable Microsoft Windows security updates released in October 2025, or subsequent updates that include the fix. Prioritize affected hosts because exploitation has been observed in the wild.
What products are affected by CVE-2025-59230?
Microsoft Corporation Windows 10 1507, Microsoft Corporation Windows 10 1607, Microsoft Corporation Windows 10 1809, Microsoft Corporation Windows 10 21h2, Microsoft Corporation Windows 10 22h2, and at least 15 more.
How severe is CVE-2025-59230?
CVE-2025-59230 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 2.7% (86th percentile) as of Oct 10, 2026.
Activity feed

Recent activity

66 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+26 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity35Community discussion across Reddit, Mastodon, and other social sources.