CVE-2025-50164
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 · uneditedHeap-based buffer overflow 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 confidenceA heap-based buffer overflow vulnerability exists in Windows Routing and Remote Access Service (RRAS) that allows an authorized attacker to execute arbitrary code over the network. The vulnerability stems from improper memory handling when processing network requests in the RRAS service, which runs with elevated privileges on Windows Server systems.
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= r2all versions= r2< 10.0.14393.8330< 10.0.17763.7678< 10.0.20348.3989< 10.0.25398.1791< 10.0.26100.4851CVSS 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.
-
Check if RRAS is installed and runningOpen Services console (services.msc) and locate 'Routing and Remote Access' service, or run 'Get-Service RemoteAccess' in PowerShell. Also check via 'Get-WindowsFeature -Name RemoteAccess' on Server CoreAffected if RRAS service is installed and running (enabled)
-
Identify Windows Server version and build numberRun 'winver' from command prompt, or execute 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' in cmd, or use 'Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion, OsHardwareAbstractionLayer' in PowerShellAffected if Version matches any of the affected ranges (Server 2008/2012 all versions, 2016 < 10.0.14393.8330, 2019 < 10.0.17763.7678, 2022 < 10.0.20348.3989, 2022 23H2 < 10.0.25398.1791, 2025 < 10.0.26100.4851)
-
Confirm RRAS feature is explicitly enabledRun 'netsh routing ip show status' or check via Server Manager > Add Roles and Features > Routing and Remote Access shows as installedAffected if RRAS role is installed or enabled on the server
-
Verify service execution contextIn Services console, double-click Routing and Remote Access service and check 'Log On' tab; verify it runs under Local System or a privileged accountAffected if Service runs with elevated privileges (default behavior for RRAS)
You are affected if RRAS is enabled on a Windows Server version within the affected build ranges listed in the CVE, as the buffer overflow requires RRAS to be running with elevated privileges.
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.833010.0.17763.767810.0.20348.3989
Apply the Microsoft security update for CVE-2025-50164 via Windows Update or enterprise patch management. Verify RRAS functionality after patching to ensure service continuity.
Upgrade to Windows Server 2019/2022/2025 and apply the corresponding cumulative update containing the fix (KB references should be obtained from Microsoft Update Catalog)
- Identify the current Windows Server version by running 'winver' or 'systeminfo' in command prompt
- Determine the appropriate target version based on your current OS: Windows Server 2016 target 10.0.14393.8330 or later, Windows Server 2019 target 10.0.17763.7678 or later, Windows Server 2022 target 10.0.20348.3989 or later, Windows Server 2022 23h2 target 10.0.25398.1791 or later, Windows Server 2025 target 10.0.26100.4851 or later
- For Windows Server 2008 or 2012 (all versions): These are end-of-life and no longer receive security patches - migrate to a supported Windows Server version (2019, 2022, or 2025)
- Backup all critical data, RRAS configurations, and registry settings before patching
- Apply the latest Windows Updates via Windows Update Catalog or WSUS for your specific server version
- Restart the server if prompted after updates install
- Verify the RRAS service is running: Open Services console and check 'Routing and Remote Access' service status
- Confirm the security update is installed by checking Windows Update history for the relevant KB article
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-50164 — 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-2025-50164 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