Skip to main content

Windows RRAS CVE-2026-70158

| EUVDEUVD-2026-100124 HIGH
Double Free (CWE-415)
2026-10-13 secure@microsoft.com GHSA-j4c5-mx55-67wp
8.8
CVSS 3.1 · Vendor: microsoft
View

Attack ChainAIDerived

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

  1. Access
    Obtain low-privilege access to RRAS endpoint
  2. Exploit
    Send crafted RRAS protocol request
  3. Execution
    Trigger double-free (CWE-415) memory corruption
  4. Impact
    Execute arbitrary code in service context

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Double free prevention
Exploitation Conditions

Exploitation requires the target Windows host to have the Routing and Remote Access Service (RRAS) role/feature installed and running, as this is the vulnerable component named in the description; RRAS is not enabled by default on standard Windows installations, which materially limits the exposed population. The CVSS vector's PR:L indicates the attacker must already hold a low-privilege/authenticated position to reach and trigger the flaw, so purely anonymous exploitation is not supported by the available data. No user interaction is required (UI:N), and the attack is network-reachable (AV:N) against systems below the listed patched build numbers.

Impact

This is a credible high-priority vulnerability. The provided CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 8.8) describes a network-reachable, low-complexity, remote code execution flaw requiring only low privileges and no user interaction, with full confidentiality, integrity, and availability impact. CWE-415 (Double Free) is consistent with a memory-corruption RCE rather than the 'Authentication Bypass' implied by the input tags - treat that tag as suspect. Exploitation signals are limited: there is NO EPSS score, NO CISA KEV listing, and NO public POC in the provided data, so per the available evidence this is 'no public exploit identified at time of analysis' and should not be described as actively exploited. The balance is a high-severity, Microsoft-reported, patch-available bug in a Windows network role with no confirmed exploitation yet; prioritize patching where the RRAS role is enabled, but there is no signal of mass or opportunistic exploitation at this time. Note: PR:L indicates the attacker needs some authenticated/low-privilege foothold, which meaningfully constrains purely anonymous remote exploitation despite AV:N.

Exploit ScenarioDerived

An attacker with a low-privileged authenticated foothold (consistent with PR:L) sends specially crafted traffic to a Windows host running the Routing and Remote Access Service, triggering a double-free memory-corruption condition. Successful exploitation yields arbitrary code execution in the context of the RRAS service with full impact to confidentiality, integrity, and availability. No public exploit code was identified in the provided intelligence.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
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

Remote code execution in the Windows Routing and Remote Access Service (RRAS) affects Windows 10, Windows 11 and Windows Server 2012 through 2025 hosts on which the RRAS role is installed, with the CVSS 3.1 vector (8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) indicating a network-reachable attacker who already holds a low-privilege authenticated position, requires no user interaction, and can achieve full confidentiality, integrity and availability impact. The defect is a double free (CWE-415) memory-corruption condition in the service, which Microsoft has addressed in its monthly update with fixed builds published for each supported branch. There is no public exploit identified at time of analysis and no confirmed actively exploited (CISA KEV) status, and real-world exposure is materially narrowed because RRAS is not enabled by default on standard Windows installations.

RemediationAI

Apply the Microsoft security update that corresponds to your Windows build: Windows 11 23H2 to 10.0.22631.7652 or later, Windows 11 24H2 / Windows Server 2025 to 10.0.26100.9711 (Server 2025: 10.0.26100.33650) or later, Windows 11 25H2 to 10.0.26200.9711, Windows 11 26H1 to 10.0.28000.3231, Windows 11 26H2 to 10.0.26300.9711, Windows 10 21H2 to 10.0.19044.7807, Windows Server 2022 to 10.0.20348.5761, Windows Server 2019 / Windows 10 1809 to 10.0.17763.9376, Windows Server 2016 / Windows 10 1607 to 10.0.14393.9612, Windows Server 2012 to 6.2.9200.26434 and Windows Server 2012 R2 to 6.3.9600.23470; installation details are in the MSRC advisory https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-70158. If a build cannot be patched immediately, the most effective compensating control is to remove the RRAS role entirely on hosts that do not need to terminate VPN or act as routers (Server Manager, 'Remove Roles and Features') - this eliminates the vulnerable component but also disables VPN termination, NAT and routing for that host, so it is only viable for systems where that functionality is dormant; where RRAS is required, restrict network reachability to the service by blocking inbound PPTP (TCP 1723 and GRE protocol 47), L2TP (UDP 1701), IKEv2 (UDP 500/4500) and remote RPC/SMB management traffic (TCP 135 and the dynamic RPC range, TCP 445) from untrusted networks, accepting that remote VPN clients will fail unless they arrive through an already-trusted gateway or VPN concentrator; because the assessed vector requires an authenticated low-privilege position, enforce least privilege for any account that can reach the service, enable MFA on VPN authentication, and disable or rotate credentials for dormant remote-access accounts - none of these compensating measures correct the memory-corruption flaw itself, so patching remains required, and if neither patching nor role removal is possible, monitor RRAS-related service crashes (faulting module in the routing/remote-access service) as a likely indicator of exploitation attempts.

Affected VersionsENISA

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

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

RRAS is the Windows component that provides routing, network address translation, remote-access VPN termination (PPTP, L2TP/IPsec, SSTP, IKEv2), demand-dial routing and dial-up remote access, and it is installed as an optional role or feature rather than being present in a default configuration. Its management surface is reachable both over the network (service listeners and RPC/SMB-based administration) and locally, which is why the assessed vector is AV:N with PR:L: the attacker must already possess a low-privilege authenticated foothold or valid credentials to reach and trigger the vulnerable code path, and no user interaction is required once that condition is met. The root cause is CWE-415, a double free - the same heap allocation is released twice, corrupting allocator metadata and creating a classic use-after-free/double-free primitive that can be shaped into arbitrary memory write and, as the vendor rates it, remote code execution in the service's security context (typically SYSTEM on a server hosting the role). Note that the EUVD record carries an 'Authentication Bypass' tag alongside 'RCE', but the authoritative CVSS vector's PR:L does not support anonymous exploitation; treat the bypass tag as catalog metadata reflecting an access-control component of the flaw rather than a pre-auth RCE claim. Because RRAS is not part of a default install, the exploitable population is limited to hosts deliberately configured as VPN/routing endpoints - disproportionately edge and infrastructure servers, which raises the value of the target despite the lower device count.

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 8.8 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

RRAS is network-reachable (AV:N) and the double-free is low-complexity (AC:L), but reaching the service realistically needs a low-privilege foothold (PR:L); RCE yields full C/I/A.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/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
Low
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:19 cve.org
HIGH 8.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 memory-corruption flaw in Microsoft's Routing and Remote Access Service (CVE-2026-70158, CVSS 8.8) allows an attacker who already holds a low-privilege account on the network to execute arbitrary code with full control over confidentiality, integrity, and availability on affected Windows 10, Windows 11, and Windows Server 2012 through 2025 systems. Only hosts with the RRAS role explicitly installed are exposed, so the immediate risk is concentrated in the networking, VPN, and remote-access infrastructure that most organizations treat as trusted edge systems. Because RRAS servers often sit on perimeter or transit paths, a single unpatched instance could give an intruder a durable foothold with broad downstream reach, making prompt prioritization a governance and resilience issue rather than a routine desktop update.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.9%
Top 43% exploitable
Prevalence
Ubiquitous
Affected product is Windows across all current client/server builds; RRAS role is optional
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Unlikely
Data Quality
5 sources
Confidence: Medium

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 HIGH
CISA KEV No
Public POC No
EPSS 0.9%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
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
No
Human Impact
High
Technical Impact
Total

Priority Score

45
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

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