Skip to main content
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach network-exposed RRAS service
  2. Delivery
    Send crafted malformed packet
  3. Exploit
    Trigger heap buffer overflow (CWE-122)
  4. Execution
    Execute arbitrary code on host
  5. Impact
    Gain full control of victim machine

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Heap buffer bounds checking
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

The Routing and Remote Access Service (RRAS) role must be installed and enabled on the target host, and its network listener must be reachable by the attacker - RRAS is NOT enabled by default on Windows, which is the primary factor limiting real-world exposure to hosts acting as VPN/routing/dial-up gateways. Where RRAS is running and network-exposed, no further conditions apply: per CVSS AV:N/AC:L/PR:N/UI:N exploitation is remote, unauthenticated, low-complexity, and requires no user interaction. Affected builds span Windows 10/11 (multiple versions) and Windows Server 2012 through 2025 below the patched build numbers listed in EUVD-2026-99519; fully patched builds are not vulnerable.

Impact

This is a genuine high-priority vulnerability, though the signals are mixed and warrant nuance. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) describes the worst case: network-reachable, low-complexity, unauthenticated, no user interaction, with total (C:H/I:H/A:H) impact via a CWE-122 heap-based buffer overflow - consistent with a 9.8 CRITICAL. CISA's SSVC framework reinforces urgency on impact (Technical Impact: total) and Automatable: yes, meaning the attack can be reliably scripted/wormable. However, SSVC Exploitation is 'none' and there is no CISA KEV listing and no identified public exploit code, so the threat today is potential rather than observed. No EPSS score was provided, so probabilistic exploitation likelihood cannot be factored in - this is a real gap. The key limiting factor NOT reflected in the CVSS score is that RRAS is an optional Windows role that is not enabled by default; the 9.8 applies only where RRAS is deployed and network-exposed. Net: treat as a priority patch for any host running RRAS (especially internet-facing VPN/routing gateways), but the ubiquitous-on-paper CVSS overstates exposure for the typical Windows estate where RRAS is absent.

Exploit ScenarioDerived

An attacker who can reach the RRAS service over the network (e.g., an internet-facing VPN/routing gateway) sends a crafted packet that triggers a heap-based buffer overflow in the RRAS parsing code, corrupting heap memory to achieve remote code execution without authentication or user interaction. Per CVSS AC:L this requires no special timing or conditions once the service is reachable. No public exploit code has been identified at time of analysis, so weaponization effort currently rests with the attacker.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
Patch available 0.9% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 14, 2026

Unauthenticated remote code execution in the Windows Routing and Remote Access Service (RRAS) allows a network attacker to run arbitrary code in the context of the RRAS service on any host where the RRAS role is installed and its listener is reachable, yielding full compromise of confidentiality, integrity and availability (CVSS 9.8, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, CWE-122 heap overflow, with an authentication-bypass component implied by the pre-auth reachability of the flaw). Exposure is severely gated by configuration rather than by exploit difficulty: RRAS is not enabled by default on Windows, so only machines acting as VPN, dial-up or routing gateways - across Windows 10/11 and Windows Server 2012 through 2025 builds older than the patched build numbers - are realistically at risk. No public exploit code has been identified at time of analysis, CISA SSVC records Exploitation: none alongside Automatable: yes and Technical Impact: total, and Microsoft has released fixes, so this should be treated as a high-priority patch item rather than an active emergency.

RemediationAI

Vendor-released patches are available from Microsoft: apply the current cumulative update for each affected platform through the MSRC update guide at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-85809, targeting at minimum build 10.0.19044.7807 for Windows 10 21H2/22H2, 10.0.14393.9612 for Windows 10 1607 and Server 2016, 10.0.17763.9376 for Windows 10 1809 and Server 2019, 10.0.20348.5761 for Server 2022, 10.0.26100.33650 for Server 2025, 10.0.26100.9711 / 10.0.26200.9711 / 10.0.26300.9711 / 10.0.22631.7652 / 10.0.28000.3231 for the respective Windows 11 releases, and 6.2.9200.26434 / 6.3.9600.23470 for Server 2012 and 2012 R2 (Server Core media included). Where patching cannot be immediate, the highest-value compensating control is reduction of attack surface: if the host does not genuinely need to terminate VPN, dial-up or routed connections, remove the Routing and Remote Access role or stop and disable the RemoteAccess service, accepting that remote access and routing functions it provided will cease; if RRAS must stay online, place host firewall rules that permit inbound traffic only from trusted client subnets and management networks rather than the internet or any untrusted segment, restricting the L2TP (UDP 1701), PPTP (TCP 1723), SSTP (TCP 443), IKEv2 (UDP 500/4500) and RRAS RPC management ports, with the trade-off that roaming or third-party VPN clients outside the allow-list will lose connectivity. Third-party compensating controls such as network IPS signatures against malformed RRAS negotiation traffic can add interim coverage but should be assumed bypassable and must not substitute for the vendor fix; there is no configuration flag that disables only the vulnerable code path, so patching or role removal remains the only complete remediation.

Affected VersionsENISA

Windows 10 Version 21H2 10.0.19044.0 <10.0.19044.7807
Windows Server 2012 R2 6.3.9600.0 <6.3.9600.23470
Windows Server 2025 10.0.26100.0 <10.0.26100.33650
Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.33650
Windows 10 Version 1607 10.0.14393.0 <10.0.14393.9612
Windows Server 2012 (Server Core installation) 6.2.9200.0 <6.2.9200.26434
Windows Server 2012 6.2.9200.0 <6.2.9200.26434
Windows 11 version 26H1 10.0.28000.0 <10.0.28000.3231
Windows 11 Version 26H2 10.0.26300.0 <10.0.26300.9711
Windows Server 2016 (Server Core installation) 10.0.14393.0 <10.0.14393.9612
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.9711
Windows 10 Version 22H2 10.0.19045.0 <10.0.19044.7807
Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.9711
Windows 10 Version 1809 10.0.17763.0 <10.0.17763.9376
Windows Server 2019 10.0.17763.0 <10.0.17763.9376
Windows Server 2016 10.0.14393.0 <10.0.14393.9612
Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.9376
Windows Server 2012 R2 (Server Core installation) 6.3.9600.0 <6.3.9600.23470
Windows Server 2022 10.0.20348.0 <10.0.20348.5761
Windows 11 Version 23H2 10.0.22631.0 <10.0.22631.7652

Affected Packages

euvd windows_10_version_1607 fix: 10.0.14393.9612
euvd windows_10_version_1809 fix: 10.0.17763.9376
euvd windows_10_version_21h2 fix: 10.0.19044.7807
euvd windows_10_version_22h2 fix: 10.0.19044.7807
euvd windows_11_version_23h2 fix: 10.0.22631.7652
euvd windows_11_version_24h2 fix: 10.0.26100.9711
euvd windows_11_version_25h2 fix: 10.0.26200.9711
euvd windows_11_version_26h1 fix: 10.0.28000.3231
euvd windows_11_version_26h2 fix: 10.0.26300.9711
euvd windows_server_2012 fix: 6.2.9200.26434
euvd windows_server_2012_r2 fix: 6.3.9600.23470
euvd windows_server_2012_r2_server_core_installation fix: 6.3.9600.23470
euvd windows_server_2012_server_core_installation fix: 6.2.9200.26434
euvd windows_server_2016 fix: 10.0.14393.9612
euvd windows_server_2016_server_core_installation fix: 10.0.14393.9612
euvd windows_server_2019 fix: 10.0.17763.9376
euvd windows_server_2019_server_core_installation fix: 10.0.17763.9376
euvd windows_server_2022 fix: 10.0.20348.5761
euvd windows_server_2025 fix: 10.0.26100.33650
euvd windows_server_2025_server_core_installation fix: 10.0.26100.33650

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 flaw is a heap-based buffer overflow (CWE-122) in the Windows Routing and Remote Access Service, the svchost-hosted component that implements Microsoft's built-in multi-protocol router, VPN server (PPTP, L2TP/IPsec, SSTP, IKEv2) and dial-up/remote-access stack, together with the RPC-based management surface used by the RRAS MMC snap-in. CWE-122 describes a write past the end of a heap-allocated buffer, typically caused by a missing or incorrect length check when copying attacker-controlled data - here likely a length field or protocol element parsed from a network packet that is trusted without validation against the destination allocation. Because the overflow lands in heap memory rather than the stack, exploitation usually requires corrupting adjacent chunk metadata or an in-heap function pointer to redirect execution, which is why the impact is scored as total (C:H/I:H/A:H) but also why a working exploit is not automatic. The pre-authentication posture - PR:N/UI:N in both the NVD and independent assessments - indicates the vulnerable parsing path is reached during protocol negotiation before any credential check, which matches the Authentication Bypass tag in the source metadata and means no valid VPN credentials or domain account are needed. No CPE identifiers were supplied in the intelligence feed, so exact platform coverage must be read from the EUVD build ranges rather than from CPE strings. Independent assessment emphasises that the RRAS role must be installed, enabled and network-reachable for the bug to be exploitable at all, and that fully patched builds are not affected; that deployment precondition, not any inherent exploit complexity, is the dominant real-world risk limiter.

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

Vendor (microsoft) PRIMARY 9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
ENISA EUVD HIGH
vuln.today AI 9.8 CRITICAL

RRAS is a network-listening service exploitable unauthenticated once enabled (AV:N/PR:N/AC:L/UI:N); heap overflow yields code execution with full C/I/A impact on the same host (S:U).

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch available
Oct 13, 2026 - 20:20 EUVD
CVE Published
Oct 13, 2026 - 19:21 cve.org
CRITICAL 9.8

DescriptionCVE.org

Remote Code Execution in Windows Routing and Remote Access Service (RRAS) allows attacker to gain an unauthorized access to victim's machine

Executive ViewAI

Why It Matters

A critical pre-authentication remote code execution flaw in the Windows Routing and Remote Access Service (RRAS) allows any network-reachable attacker to take full control of affected hosts, with complete loss of confidentiality, integrity, and availability. The exposure is limited to Windows 10/11 and Windows Server 2012 through 2025 systems that have the RRAS role explicitly installed and its listener reachable - typically VPN, dial-up, and routing gateways - so organizations running remote-access infrastructure should treat this as a priority remediation item while the broader Windows estate remains largely unaffected. Because no public exploit code has been identified at time of analysis, leadership has a narrow window to patch internet-facing gateways before exploitation tooling emerges.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.9%
Top 40% exploitable
Prevalence
Ubiquitous
Core Windows OS component across all supported client and server editions
Threat Intel
1
1 sources
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Less Likely
Data Quality
6 sources
Confidence: High

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.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.9%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Total

Priority Score

55
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +49
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: +5

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

A heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

CVE-2025-52691 CRITICAL POC
10.0 Dec 29

Unauthenticated remote code execution in SmarterTools SmarterMail lets an attacker upload arbitrary files to any locatio

CVE-2019-0803 HIGH POC
7.8 Apr 09

Windows Win32k fails to properly handle objects in memory, allowing local privilege escalation exploited in the wild in

CVE-2020-1472 MEDIUM POC
5.5 Aug 17

A privilege escalation vulnerability (CVSS 5.5). Risk factors: actively exploited (KEV-listed), EPSS 94% exploitation pr

CVE-2025-33053 HIGH POC
8.8 Jun 10

Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables

CVE-2025-33073 HIGH POC
8.8 Jun 10

Windows SMB contains an improper access control vulnerability (CVE-2025-33073, CVSS 8.8) enabling authenticated attacker

CVE-2025-13315 CRITICAL POC
9.3 Nov 19

Twonky Server 8.5.2 on Linux and Windows allows unauthenticated access to the admin log file through a web service API b

CVE-2013-10047 CRITICAL POC
9.3 Aug 01

An unrestricted file upload vulnerability exists in MiniWeb HTTP Server <= Build 300 that allows unauthenticated remote

CVE-2012-10030 CRITICAL POC
9.3 Aug 05

FreeFloat FTP Server contains multiple critical design flaws that allow unauthenticated remote attackers to upload arbit

CVE-2025-34101 CRITICAL POC
9.3 Jul 10

Serviio Media Server versions 1.4 through 1.8 on Windows contain an unauthenticated command injection in the /rest/actio

CVE-2025-13316 HIGH POC
8.2 Nov 19

Twonky Server 8.5.2 uses hard-coded cryptographic keys for encrypting the administrator password. Combined with the cred

CVE-2025-34095 CRITICAL POC
9.3 Jul 10

Mako Server versions 2.5 and 2.6 contain an unauthenticated OS command injection via the tutorial interface at examples/

CVE-2025-11953 CRITICAL POC
9.8 Nov 03

React Native Metro Development Server binds to external interfaces by default and contains an OS command injection endpo

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy