dbcve.org
Windows Server 2008Operating system · Microsoft

CVE-2025-50156

MEDIUM · 5.7 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 →
61/100
Remediation priority · Elevated
Remotely reachable

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
Use of uninitialized resource in Windows Routing and Remote Access Service (RRAS) allows an authorized attacker to disclose information 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

CVE-2025-50156 is an information disclosure vulnerability in Windows Routing and Remote Access Service (RRAS) caused by the use of an uninitialized resource. An authenticated attacker can exploit this to disclose sensitive information over a network. The CVSS 5.7 indicates limited impact, likely revealing small amounts of contextual data rather than critical secrets.

MitigationApply Microsoft security updates for this vulnerability to all affected Windows servers running RRAS. If immediate patching is not possible, consider restricting network access to RRAS and limiting which authenticated users can interact with the service.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N

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. Confirm Windows Server OS is running
    Run 'winver' or check system properties to verify the OS is Windows Server (not Windows client). This vulnerability only affects Windows Server editions.
    Affected if The system is running a Windows Server edition listed in the affected versions.
  2. Verify RRAS role is installed
    Open Server Manager > Add Roles and Features, or run 'Get-WindowsFeature -Name RemoteAccess' in PowerShell to check if the Remote Access server role (which includes RRAS) is installed.
    Affected if The Remote Access server role is installed on the system.
  3. Confirm RRAS service is enabled and running
    Open Services console (services.msc) and check the 'Routing and Remote Access' service status, or run 'Get-Service RemoteAccess' in PowerShell.
    Affected if The RemoteAccess service is installed, running, or set to start automatically.
  4. Check installed Windows build version
    Run 'winver', 'systeminfo | findstr /C:"Build"', or 'ver' command in cmd.exe to obtain the exact Windows build number (for example, 10.0.17763.7678).
    Affected if A build version is returned that falls below the fixed versions for the detected Windows Server release.
  5. Compare build against fixed versions
    Cross-reference the detected build number with the fixed versions: Server 2016 requires 10.0.14393.8330 or higher; Server 2019 requires 10.0.17763.7678 or higher; Server 2022 requires 10.0.20348.3989 or higher; Server 2022 23h2 requires 10.0.25398.1791 or higher; Server 2025 requires 10.0.26100.4851 or higher. For Server 2008/2012 (all versions), no patch is listed.
    Affected if The installed build version is lower than the required fixed version for the corresponding Windows Server release, or the system runs Server 2008/2012 where all versions are affected.

A system is affected if it runs any affected Windows Server version with the RRAS role installed and enabled, and the installed build version falls below the specified fixed version for that Windows Server release.

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 to all affected Windows servers running RRAS. If immediate patching is not possible, consider restricting network access to RRAS and limiting which authenticated users can interact with the service.

Recommended fix High confidence

Apply Microsoft security update KB for CVE-2025-50156 - fixed builds: 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)

  1. Identify the Windows Server version and build number by running 'winver' or 'systeminfo' on the affected server
  2. Locate the appropriate Microsoft security update for CVE-2025-50156 by searching the Microsoft Security Response Center (msrc.microsoft.com) catalog
  3. Apply the security update via Windows Update, WSUS, or by manually downloading and installing the specific KB patch for your Windows Server version
  4. Restart the server if required by the update installation
  5. Verify the update was successfully installed by checking the installed updates list or running 'systeminfo' to confirm the build number matches or exceeds the fixed version threshold
Caveat Apply during planned maintenance window as server restart may be required; RRAS service may briefly interrupt during patch installation

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

Fix this in Windows Server 2008 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-50156 — 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-50156 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