dbcve.org
Windows Server 2008Operating system · Microsoft

CVE-2025-53148

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 is a use of uninitialized resource vulnerability in Windows Routing and Remote Access Service (RRAS). The vulnerability allows an authorized attacker to disclose information over a network by leveraging memory or resources that have not been properly initialized before use. The required authorization level is not specified, but the attacker must have some form of authenticated access to the RRAS service.

MitigationApply the relevant Microsoft security patches for this vulnerability through Windows Update. Additionally, restrict network access to RRAS services to only authorized personnel and ensure proper authentication mechanisms are enforced.

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
    Open Server Manager, go to Manage > Add Roles and Features, check if 'Remote Access' role with 'Routing' role services is installed. Alternatively, run `Get-WindowsFeature -Name Routing` in PowerShell on Server editions, or check for the RemoteAccess service via `sc query RemoteAccess`.
    Affected if RRAS is installed and the Windows Server version falls within the affected ranges (Server 2008/2012 all versions; 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)
  2. Confirm Windows Server version
    Run `winver`, or execute `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"` in Command Prompt, or use `Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion` in PowerShell. Note the exact build number (for example, 10.0.14393.8330).
    Affected if The installed Windows Server version matches one of the affected product versions and is lower than the corresponding fixed build number.
  3. Check if RemoteAccess service is running
    Open Services.msc and locate the 'Remote Access (RRAS)' service, or run `sc query RemoteAccess` in Command Prompt. Verify the service status (RUNNING, STOPPED, etc.).
    Affected if The RemoteAccess service is running or set to start, making the RRAS interface accessible over the network.

You are affected if RRAS is installed/enabled and your Windows Server version is below the specified build numbers for your product, as the vulnerability requires an active RRAS service to be exploited.

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 relevant Microsoft security patches for this vulnerability through Windows Update. Additionally, restrict network access to RRAS services to only authorized personnel and ensure proper authentication mechanisms are enforced.

Recommended fix High confidence

Apply the Microsoft security update containing the fix for CVE-2025-53148 (build thresholds: WS2016 >=10.0.14393.8330, WS2019 >=10.0.17763.7678, WS2022 >=10.0.20348.3989, WS2022 23h2 >=10.0.25398.1791, WS2025 >=10.0.26100.4851)

  1. Check current Windows Server version by running 'winver' or 'systeminfo' in command prompt
  2. Open Settings > Update & Security > Windows Update or run 'ms-settings:windowsupdate'
  3. Click 'Check for updates' to download and install the latest security patches
  4. If running Windows Server 2016/2019/2022, ensure the installed build number is at least 10.0.14393.8330 / 10.0.17763.7678 / 10.0.20348.3989 respectively
  5. For Windows Server 2022 23h2, ensure build is at least 10.0.25398.1791
  6. For Windows Server 2025, ensure build is at least 10.0.26100.4851
  7. Restart the server if prompted to complete the update installation
  8. Verify the installed updates include the security patch for CVE-2025-53148 by checking Windows Update history
Caveat Standard security update; no expected breaking changes for this informational disclosure patch

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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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