LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25172: Windows Routing and Remote Access Service (RRAS) Remote Code Execution Vulnerability

Integer overflow or wraparound in Windows Routing and Remote Access Service (RRAS) allows an authorized attacker to execute code over a network.

HighCVSS 8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-25172 is a high-severity Windows RRAS flaw. An authorized network attacker could potentially run code on affected Windows systems. It matters most where RRAS is enabled for VPN, routing, or remote access roles. Microsoft lists an update, and there is no provided evidence of active exploitation.

Executive priority

Treat as a priority patching item for organizations using Microsoft RRAS. The business risk is possible code execution on remote-access infrastructure, which can be high-value. Urgency is high for exposed RRAS servers, but current sources do not support claims of active exploitation.

Technical view

The issue is an integer overflow or wraparound in Windows Routing and Remote Access Service, mapped to CWE-190 and CWE-122. Microsoft rates it CVSS 8.0, with network attack vector, low complexity, low privileges required, user interaction required, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to affected Windows client and server versions where RRAS is installed or enabled. Internet-facing or broadly reachable RRAS deployments have higher priority. Systems not using RRAS are less likely to be exposed, but should still be verified against Microsoft’s affected-products list.

Exploitation context

The source bundle does not show CISA KEV listing or public evidence of active exploitation. CVSS indicates exploitation requires an authorized attacker, network access, low privileges, and user interaction. Microsoft’s exploit maturity field is listed as unproven in the provided data.

Researcher notes

Key constraints are PR:L and UI:R despite network reachability. The advisory identifies integer overflow/wraparound with potential heap overflow implications. Public detail is limited in the provided sources; avoid assuming protocol specifics, proof-of-concept availability, or exploitation in the wild without additional evidence.

Mitigation direction

  • Review Microsoft’s CVE-2026-25172 advisory and apply the listed security update.
  • Prioritize RRAS servers, VPN gateways, and remotely reachable Windows Server systems.
  • Restrict network access to RRAS services where business operations allow.
  • Disable RRAS where it is not required.
  • Monitor Microsoft guidance for revised affected versions or additional mitigations.

Validation and detection

  • Inventory Windows systems running RRAS or remote access roles.
  • Compare OS versions against Microsoft’s affected-products list.
  • Confirm the relevant Microsoft security update is installed.
  • Review exposure of RRAS endpoints to untrusted networks.
  • Check logs for unusual authenticated RRAS activity, without assuming exploitation.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-122: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-190: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-25172 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C2.15.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8High
CVSS 3.1 vector shape for CVE-2026-25172Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftWindows 10 Version 160710.0.14393.0Listed
MicrosoftWindows 10 Version 180910.0.17763.0Listed
MicrosoftWindows 10 Version 21H210.0.19044.0Listed
MicrosoftWindows 10 Version 22H210.0.19045.0Listed
MicrosoftWindows 11 version 22H310.0.22631.0Listed
MicrosoftWindows 11 Version 23H210.0.22631.0Listed
MicrosoftWindows 11 Version 24H210.0.26100.0Listed
MicrosoftWindows 11 Version 25H210.0.26200.0Listed
MicrosoftWindows 11 version 26H110.0.28000.0Listed
MicrosoftWindows Server 20126.2.9200.0Listed
MicrosoftWindows Server 2012 (Server Core installation)6.2.9200.0Listed
MicrosoftWindows Server 2012 R26.3.9600.0Listed
MicrosoftWindows Server 2012 R2 (Server Core installation)6.3.9600.0Listed
MicrosoftWindows Server 201610.0.14393.0Listed
MicrosoftWindows Server 2016 (Server Core installation)10.0.14393.0Listed
MicrosoftWindows Server 201910.0.17763.0Listed
MicrosoftWindows Server 2019 (Server Core installation)10.0.17763.0Listed
MicrosoftWindows Server 202210.0.20348.0Listed
MicrosoftWindows Server 2022, 23H2 Edition (Server Core installation)10.0.25398.0Listed
MicrosoftWindows Server 202510.0.26100.0Listed
MicrosoftWindows Server 2025 (Server Core installation)10.0.26100.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-122 · source CWE mapping

Heap-based Buffer Overflow

Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-190 · source CWE mapping

Integer Overflow or Wraparound

Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.