dbcve.org
Windows Server 2008Operating system · Microsoft

CVE-2025-50163

HIGH · 8.8 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 10.0.14393.8330 / 10.0.17763.7678 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Heap-based buffer overflow in Windows Routing and Remote Access Service (RRAS) allows an unauthorized 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 confidence

Heap-based buffer overflow vulnerability in Windows Routing and Remote Access Service (RRAS) enables remote unauthenticated attackers to execute arbitrary code by overflowing heap memory in the network service component.

MitigationApply Microsoft security updates for this vulnerability when released; until then, disable RRAS if not required, restrict network access to RRAS-enabled servers, and implement network segmentation.

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 data
Windows Server 2008Operating system
Affected:all versions= r2
Windows Server 2012Operating system
Affected:all versions= r2
Windows Server 2016Operating system
Affected:< 10.0.14393.8330
Windows Server 2019Operating system
Affected:< 10.0.17763.7678
Windows Server 2022Operating system
Affected:< 10.0.20348.3989
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1791
Windows Server 2025Operating system
Affected:< 10.0.26100.4851

CVSS 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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify if RRAS role is installed
    On the server, open Server Manager, go to Manage > Add Roles and Features, or run 'Get-WindowsFeature -Name Routing' in PowerShell to check if the Routing role is installed.
    Affected if RRAS (Routing and Remote Access Service) role is installed on the server.
  2. Confirm RRAS service is running
    Open Services console (services.msc) or run 'Get-Service RemoteAccess' in PowerShell. Check if the RemoteAccess service status is Running.
    Affected if The RemoteAccess service is running, indicating RRAS is active.
  3. Check Windows build number
    Run 'winver' from the command line, or run 'systeminfo | findstr /C:"Build"' in cmd, or '[System.Environment]::OSVersion.Version' in PowerShell to obtain the exact build number.
    Affected if The build number is lower than the affected thresholds: Server 2016 < 10.0.14393.8330, Server 2019 < 10.0.17763.7678, Server 2022 < 10.0.20348.3989, Server 2022 23h2 < 10.0.25398.1791, Server 2025 < 10.0.26100.4851. Server 2008 and 2012 are all affected regardless of build.

The server is affected if RRAS is installed and running AND the Windows build number falls within the affected versions (or is Server 2008/2012 any version).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 10.0.14393.8330 / 10.0.17763.7678 / 10.0.20348.3989 or later
Fixed in 10.0.14393.833010.0.17763.767810.0.20348.3989
Interim mitigation

Apply Microsoft security updates for this vulnerability when released; until then, disable RRAS if not required, restrict network access to RRAS-enabled servers, and implement network segmentation.

Recommended fix High confidence

Windows Server 2016: 10.0.14393.8330+ | Windows Server 2019: 10.0.17763.7678+ | Windows Server 2022: 10.0.20348.3989+ | Windows Server 2022 23h2: 10.0.25398.1791+ | Windows Server 2025: 10.0.26100.4851+

  1. Check current Windows Server version by running 'winver' or 'systeminfo' in Command Prompt
  2. Identify the applicable security update for CVE-2025-50163 from Microsoft Security Response Center (msrc.microsoft.com)
  3. Apply the Microsoft security update for this CVE through Windows Update, WSUS, or by downloading the update from the Microsoft Update Catalog
  4. Restart the server after applying the update
  5. Verify the update was successfully installed by checking 'Installed Updates' or running 'systeminfo' to confirm the build number matches or exceeds the fixed version for your Windows Server version
Caveat Windows Server 2008 and 2012 are end-of-life and no longer receive security updates from Microsoft - consider migrating to a supported Windows Server version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows Server 2008 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-50163 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-50163 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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