dbcve.org
Windows Server 2008Operating system · Microsoft

CVE-2025-53797

MEDIUM · 6.5 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 10.0.14393.8422 / 10.0.17763.7792 or later.
See remediation →
72/100
Remediation priority · Elevated
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
Buffer over-read in Windows Routing and Remote Access Service (RRAS) allows an unauthorized 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

A buffer over-read vulnerability exists in Windows Routing and Remote Access Service (RRAS) that allows an unauthenticated attacker on the network to read memory contents beyond allocated buffer boundaries, potentially disclosing sensitive information. The flaw requires network access to the affected RRAS service and does not require authentication to exploit.

MitigationApply the Microsoft security update for CVE-2025-53797 once available, or disable RRAS if not required in the environment, and restrict network access to RRAS ports via firewall rules as a defense-in-depth measure.

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.8422
Windows Server 2019Operating system
Affected:< 10.0.17763.7792
Windows Server 2022Operating system
Affected:< 10.0.20348.4106
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1849
Windows Server 2025Operating system
Affected:< 10.0.26100.6508

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 role is installed
    Open Server Manager, go to Manage > Add Roles and Features, check if 'Remote Access' role with 'Routing' role service is installed. Or run 'Get-WindowsFeature -Name Routing' in PowerShell on the server.
    Affected if RRAS role is installed and the Routing role service is enabled
  2. Confirm Windows Server version falls within affected range
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get the exact Windows build number. Compare against: Server 2008 (all), Server 2012 (all), Server 2012 R2 (all), Server 2016 < 10.0.14393.8422, Server 2019 < 10.0.17763.7792, Server 2022 < 10.0.20348.4106, Server 2022 23h2 < 10.0.25398.1849, Server 2025 < 10.0.26100.6508
    Affected if Windows Server version is lower than the specific build number for that release family
  3. Check if RRAS service is running and listening on network
    Run 'Get-Service RemoteAccess' in PowerShell to check service status. Run 'netstat -ano | findstr "1723 1701 47"' to check for RRAS-related listening ports (PPTP, L2TP, GRE).
    Affected if RemoteAccess service is running and bound to network-facing ports
  4. Verify RRAS is network-accessible
    From an external system, attempt to reach RRAS ports: 1723 (PPTP), 1701 (L2TP), or test GRE (protocol 47). Use 'Test-NetConnection -ComputerName <server> -Port 1723' from a remote host.
    Affected if RRAS ports are open and reachable from untrusted networks

System is affected if RRAS Routing role is installed on an unpatched Windows Server version within the affected build ranges and the service is network-accessible.

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.8422 / 10.0.17763.7792 / 10.0.20348.4106 or later
Fixed in 10.0.14393.842210.0.17763.779210.0.20348.4106
Interim mitigation

Apply the Microsoft security update for CVE-2025-53797 once available, or disable RRAS if not required in the environment, and restrict network access to RRAS ports via firewall rules as a defense-in-depth measure.

Recommended fix High confidence

Upgrade to the specified build number or later for your Windows Server version via Windows Update or Microsoft Update Catalog

  1. Identify the current Windows Server version by running `winver` or `systeminfo` in Command Prompt
  2. Determine which version band your server falls into (2008, 2012 R2, 2016, 2019, 2022, 2022 23h2, or 2025)
  3. For Windows Server 2016: upgrade to build 10.0.14393.8422 or later
  4. For Windows Server 2019: upgrade to build 10.0.17763.7792 or later
  5. For Windows Server 2022: upgrade to build 10.0.20348.4106 or later
  6. For Windows Server 2022 23h2: upgrade to build 10.0.25398.1849 or later
  7. For Windows Server 2025: upgrade to build 10.0.26100.6508 or later
  8. Apply the latest Windows Updates via Settings > Update & Security > Windows Update, or run `Get-WindowsUpdate` in PowerShell with admin privileges
Caveat Review compatibility notes for major version upgrades; test updates in a staging environment before production deployment

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-53797 — 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-53797 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