CVE-2026-25172
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInteger overflow or wraparound in Windows Routing and Remote Access Service (RRAS) allows an authorized attacker to execute code over a network.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceInteger overflow vulnerability in Windows Routing and Remote Access Service (RRAS) allows an authenticated attacker to execute arbitrary code. The flaw stems from improper input validation in memory handling within the RRAS service, leading to heap corruption and potential remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versions= r2< 10.0.14393.8957< 10.0.17763.8511< 10.0.20348.4830< 10.0.25398.2207< 10.0.26100.32463CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify RRAS role installation statusRun 'Get-WindowsFeature -Name Routing' in PowerShell on Windows Server, or check 'Programs and Features' > 'Windows Features' > 'Remote Access' > 'Routing' on desktop Windows variantsAffected if RRAS is installed and enabled - the vulnerability only applies when the Routing and Remote Access service is present and active
-
Confirm RRAS service is runningRun 'Get-Service RemoteAccess' in PowerShell or check Services.msc for the 'Remote Access' service statusAffected if The RemoteAccess service is in a Running state - the vulnerability is only exploitable when the service is actively running
-
Check Windows Server build numberRun 'winver' from command prompt or 'Get-ComputerInfo | Select-Object OsBuildNumber,OsVersion' in PowerShellAffected if The build number falls within any of these vulnerable ranges: Server 2016 < 14393.8957, Server 2019 < 17763.8511, Server 2022 < 20348.4830, Server 2022 23h2 < 25398.2207, Server 2025 < 26100.32463 (Server 2012 R2 is vulnerable at all versions)
-
Confirm RRAS routing functionality is configuredCheck RRAS snap-in (rrasmgmt.msc) or run 'netsh routing ip show config' to see if any routing interfaces are configuredAffected if Any routing interfaces or protocols (RIP, OSPF, etc.) are configured and active - exploitation requires the routing component to be exposed
Your environment is affected if the RemoteAccess (RRAS) service is installed AND running AND your Windows Server build number is below the fixed versions listed (or is any version of Server 2012 R2).
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped10.0.14393.895710.0.17763.851110.0.20348.4830
Apply Microsoft security updates for Windows RRAS once released. Restrict network access to RRAS services to authorized personnel only until patch deployment.
Upgrade to the fixed build version for your Windows Server release: 10.0.14393.8957 (Server 2016), 10.0.17763.8511 (Server 2019), 10.0.20348.4830 (Server 2022), 10.0.25398.2207 (Server 2022 23h2), or 10.0.26100.32463 (Server 2025); Windows Server 2012/2012 R2 requires migration to a supported versio
- Check current Windows Server version by running 'winver' or 'systeminfo' in Command Prompt
- Identify the specific Windows Server version (2012, 2016, 2019, 2022, 2022 23h2, or 2025)
- For Windows Server 2012/2012 R2: Upgrade to a supported Windows Server version as these are end-of-life with no patch available
- For Windows Server 2016: Install update to build 10.0.14393.8957 or later via Windows Update or WSUS
- For Windows Server 2019: Install update to build 10.0.17763.8511 or later via Windows Update or WSUS
- For Windows Server 2022: Install update to build 10.0.20348.4830 or later via Windows Update or WSUS
- For Windows Server 2022 23h2: Install update to build 10.0.25398.2207 or later via Windows Update or WSUS
- For Windows Server 2025: Install update to build 10.0.26100.32463 or later via Windows Update or WSUS
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25172 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-25172 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data