dbcve.org
Windows Server 2008Operating system · Microsoft

CVE-2025-53138

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

This vulnerability in Windows Routing and Remote Access Service (RRAS) involves the use of an uninitialized resource, which allows an authorized attacker to disclose information over a network. The flaw stems from the service not properly initializing memory or data structures before using them, potentially exposing sensitive data from memory to network attackers.

MitigationApply the Microsoft security update for CVE-2025-53138 to affected Windows Server systems running RRAS. Until the patch is available, consider network segmentation to limit RRAS exposure and monitor for anomalous network activity.

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. Verify RRAS is installed on the system
    Open Services (services.msc) and look for 'Routing and Remote Access' service, or check the Windows Features list for 'Remote Access' role installation
    Affected if RRAS is installed and the Windows version falls within the affected version ranges
  2. Confirm RRAS service is running or enabled
    Check the service status in Services console or run 'Get-Service RemoteAccess' in PowerShell. Also check if the service is set to start automatically
    Affected if The RemoteAccess/RRAS service is running or configured to start
  3. Identify the exact Windows Server build number
    Run 'winver' or 'systeminfo' from command prompt, or run 'Get-ComputerInfo | Select-Object WindowsVersion, OsBuildNumber' in PowerShell. Note the full build number (e.g., 10.0.17763.7678)
    Affected if Build number is below the threshold for the respective Windows Server version (2016: <14393.8330, 2019: <17763.7678, 2022: <20348.3989, 2022 23h2: <25398.1791, 2025: <26100.4851) or if running Server 2008/2012 (all versions affected)
  4. Check if RRAS is configured to accept remote connections
    Open Routing and Remote Access console (rrasmgmt.msc) or check registry key HKLM\SYSTEM\CurrentControlSet\Services\RemoteAccess\Parameters for configuration state
    Affected if RRAS is configured and listening for remote/network connections

The environment is affected if RRAS is installed/enabled AND the Windows Server version/build falls within the vulnerable ranges (all Server 2008/2012 versions, or Server 2016-2025 builds below their respective thresholds).

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 the Microsoft security update for CVE-2025-53138 to affected Windows Server systems running RRAS. Until the patch is available, consider network segmentation to limit RRAS exposure and monitor for anomalous network activity.

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. For Windows Server 2016: Upgrade to build 10.0.14393.8330 or later via Windows Update or WSUS
  2. For Windows Server 2019: Upgrade to build 10.0.17763.7678 or later via Windows Update or WSUS
  3. For Windows Server 2022: Upgrade to build 10.0.20348.3989 or later via Windows Update or WSUS
  4. For Windows Server 2022 23h2: Upgrade to build 10.0.25398.1791 or later via Windows Update or WSUS
  5. For Windows Server 2025: Upgrade to build 10.0.26100.4851 or later via Windows Update or WSUS
  6. For Windows Server 2008/2008 R2 and Windows Server 2012/2012 R2: These versions are end-of-life and receive no security updates; migrate to a supported Windows Server version or apply network-level mitigations such as restricting RRAS access to trusted networks only
Caveat Windows Server 2008/2008 R2 and 2012/2012 R2 have no security patches available; these end-of-life systems require replacement

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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