Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach RPC Endpoint Mapper on TCP 135
-
ExploitSend sustained crafted RPC requests
-
ExecutionExhaust service resources (CWE-770)
-
ImpactDenial of service on Windows host
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V2 - Validation and Business Logic Resource allocation limits
MITRE ATT&CK
1 technique across 1 tactic: Impact The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The RPC Endpoint Mapper service (TCP port 135) must be network-reachable from the attacker; no authentication (PR:N) or user interaction (UI:N) is required. However, AC:H means exploitation is NOT a single-shot trigger against default settings - it requires conditions outside the attacker's full control, consistent with resource exhaustion that needs sustained or precisely-timed request volume to deplete service resources. Limiting factors: impact is availability-only (service outage, no data or integrity loss); port 135 is typically firewalled from the internet and exposed mainly on internal/enterprise networks, so realistic exposure is usually internal attackers or compromised internal hosts rather than the open internet. |
| Impact | This is a medium-severity availability-only flaw (CVSS 5.9) whose real-world priority is modest, and multiple independent signals agree on that. The CVSS vector (AV:N/PR:N/UI:N) confirms a network-reachable, unauthenticated trigger, but AC:H indicates the attacker does not fully control the conditions needed to succeed - typical of resource-exhaustion bugs (CWE-770) that require sustained or specifically-timed request patterns rather than a single packet. CISA's SSVC framework reinforces low urgency: Exploitation=none (no observed activity), Automatable=no, and Technical Impact=partial. No KEV listing and no public POC were provided, so exploitation status is speculative-at-best. EPSS is NOT present in the input and cannot be assessed - this is a gap, not a low score. Impact is strictly availability (C:N/I:N/A:H, Scope:Unchanged): no data disclosure, no code execution, no lateral movement. Net assessment: a patch-in-normal-cycle issue, not an emergency. The main thing that would elevate it is exposure of RPC Endpoint Mapper (TCP 135) directly to the internet, which is poor practice and uncommon in hardened environments. |
| Exploit ScenarioDerived | A remote, unauthenticated attacker with network reachability to TCP port 135 sends a stream of crafted RPC Endpoint Mapper requests designed to consume server resources, eventually rendering the RPC locator/mapper service unresponsive and disrupting dependent services on the target Windows host. The AC:H rating implies this requires sustained or carefully-timed traffic rather than a single request, so it is a degradation/outage condition rather than instant takedown. No public exploit code was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Uncontrolled resource consumption in the Windows RPC Endpoint Mapper service (listening on TCP 135) allows an unauthenticated, remote attacker to deny service over a network by exhausting service resources. Rated CVSS 5.9 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H), the impact is availability-only and the High attack complexity means an outage is not achievable with a single trigger against default configurations, but requires sustained or precisely timed request volume. The affected surface spans Windows Server 2012 through Server 2025 (including Server Core) plus Windows 10 1607/1809/21H2/22H2 and Windows 11 23H2 through 26H2; no public exploit code and no confirmed active exploitation have been identified at time of analysis, and Microsoft has published a vendor update guide.
RemediationAI
Patch status per vendor: Patch available per vendor advisory - Microsoft has released updates for this issue through the MSRC update guide at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-96300, and the affected-range data indicates the fix is delivered by moving each platform to a build at or above the listed thresholds (for example 10.0.26100.33650 for Windows Server 2025, 10.0.20348.5761 for Windows Server 2022, 10.0.17763.9376 for Windows Server 2019 and Windows 10 1809, 10.0.14393.9612 for Windows Server 2016 and Windows 10 1607, 10.0.19044.7807 for Windows 10 21H2/22H2, and 6.2.9200.26434 / 6.3.9600.23470 for the legacy Server 2012 and 2012 R2 branches); apply the corresponding cumulative or security-only update rather than assuming a version number. Because no public exploit code has been identified and CISA SSVC rates exploitation as none with automatability as no, this should be scheduled as routine monthly patching rather than emergency change, prioritising internet- or partner-exposed hosts and domain controllers. As a compensating control where patching must be deferred, restrict inbound TCP 135 with host and perimeter firewalls so only trusted management subnets and RPC-dependent systems can reach the Endpoint Mapper - note this will break RPC/DCOM, WMI, DFS, Exchange, and remote administration traffic that legitimately uses dynamic endpoints unless you also scope the necessary high-port ranges, so validate against a staging environment first. Disabling or unregistering the Endpoint Mapper is not a viable mitigation on Windows because it is an OS-integral service, and blocking port 135 broadly on servers introduces significant operational fallout; segmenting the network and monitoring for abnormal connection volume to TCP 135 are lower-impact alternatives that reduce the sustained request volume needed to trigger exhaustion.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 20 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The RPC Endpoint Mapper (epmapper) is the Windows RPC service bound to TCP port 135 that clients query to resolve which dynamic endpoint a given RPC interface UUID is listening on; it is a foundational component for DCOM, WMI, domain operations, DFS, and many enterprise management tools. The root cause class is CWE-770 (Allocation of Resources Without Limits or Throttling), meaning the service accepts client-driven work or internal allocations without enforcing adequate caps or backpressure, so repeated or synchronized lookups can starve the process of resources until it stops responding. The CVSS vector (AV:N/PR:N/UI:N but AC:H) confirms reachability from the network without credentials or user interaction while also indicating that exploitation depends on conditions outside the attacker's full control, consistent with a resource-exhaustion pattern rather than a deterministic single-packet crash. The service's impact is limited to availability (C:N/I:N/A:H) and CISA's SSVC decision data classifies technical impact as partial and automatability as no, so the practical risk concentrates on hosts where port 135 is reachable.
Know when Windows gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Network-reachable and unauthenticated (AV:N/PR:N/UI:N); AC:H because resource exhaustion needs sustained/timed conditions; availability-only impact (A:H, C:N/I:N) with no scope change.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Uncontrolled resource consumption in RPC Endpoint Mapper Service allows an unauthorized attacker to deny service over a network.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
Unauthenticated remote code execution in SmarterTools SmarterMail lets an attacker upload arbitrary files to any locatio
Windows Win32k fails to properly handle objects in memory, allowing local privilege escalation exploited in the wild in
A privilege escalation vulnerability (CVSS 5.5). Risk factors: actively exploited (KEV-listed), EPSS 94% exploitation pr
Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables
Windows SMB contains an improper access control vulnerability (CVE-2025-33073, CVSS 8.8) enabling authenticated attacker
An unrestricted file upload vulnerability exists in MiniWeb HTTP Server <= Build 300 that allows unauthenticated remote
FreeFloat FTP Server contains multiple critical design flaws that allow unauthenticated remote attackers to upload arbit
Serviio Media Server versions 1.4 through 1.8 on Windows contain an unauthenticated command injection in the /rest/actio
Mako Server versions 2.5 and 2.6 contain an unauthenticated OS command injection via the tutorial interface at examples/
React Native Metro Development Server binds to external interfaces by default and contains an OS command injection endpo
Command injection in the Windows Shell lets remote, unauthenticated attackers bypass a Windows security feature and then
External control of file name or path in Windows NTLM allows an unauthorized attacker to perform spoofing over a network
EUVD-2026-100220
GHSA-wcq4-23p2-jp2q
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB