dbcve.org
Windows Server 2008Operating system · Microsoft

CVE-2025-53806

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 in Windows Routing and Remote Access Service (RRAS) allows unauthenticated network attackers to read sensitive memory contents, leading to information disclosure. The flaw exists in how RRAS handles certain network packets.

MitigationApply Microsoft security updates for CVE-2025-53806 to affected Windows systems running RRAS. If immediate patching is not feasible, restrict network access to RRAS or disable the service if not required.

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 if RRAS role is installed
    On the target Windows Server, open Server Manager > Add Roles and Features, or run 'Get-WindowsFeature -Name Routing' in PowerShell to check if the Remote Access role with Routing role service is installed.
    Affected if The Remote Access server role (including Routing role service) is installed on the server.
  2. Check if RRAS service is running
    Open Services console (services.msc) and locate 'Routing and Remote Access' service, or run 'Get-Service RemoteAccess' in PowerShell.
    Affected if The RemoteAccess service is in a Running state.
  3. Determine Windows Server version and build number
    Run 'winver' command, or in PowerShell run 'Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion, OsHardwareAbstractionLayer' to obtain the exact OS version and build number.
    Affected if The Windows Server version falls within these affected ranges: Server 2008 (any version), Server 2012 (any version), Server 2016 < build 14393.8422, Server 2019 < build 17763.7792, Server 2022 < build 20348.4106, Server 2022 23h2 < build 25398.1849, Server 2025 < build 26100.6508.
  4. Confirm RRAS is configured and accepting connections
    Open Routing and Remote Access console (rrasmgmt.msc) or check registry key 'HKLM\SYSTEM\CurrentControlSet\Services\RemoteAccess\Parameters' to see if RRAS is configured/enabled for remote connections.
    Affected if RRAS is configured and enabled to accept remote connections, making the vulnerable packet handling code reachable from the network.

A system is affected if it runs a vulnerable Windows Server version from the list above, has the RRAS role installed, and has the RemoteAccess service enabled and configured to accept connections.

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 Microsoft security updates for CVE-2025-53806 to affected Windows systems running RRAS. If immediate patching is not feasible, restrict network access to RRAS or disable the service if not required.

Recommended fix High confidence

Upgrade to Windows Server 2016 build 10.0.14393.8422 or later; Windows Server 2019 build 10.0.17763.7792 or later; Windows Server 2022 build 10.0.20348.4106 or later; Windows Server 2022 23h2 build 10.0.25398.1849 or later; Windows Server 2025 build 10.0.26100.6508 or later. For Server 2008/2012, mi

  1. Identify the current Windows Server version by running 'winver' or 'systeminfo' in command prompt
  2. Determine which build version your server is running (e.g., for Server 2019, check if below 10.0.17763.7792)
  3. For Windows Server 2008 and 2012 (all versions): These are end-of-life and no longer receive security patches; plan migration to a supported Windows Server version
  4. For supported versions (2016, 2019, 2022, 2022 23h2, 2025): Apply the Microsoft security update for CVE-2025-53806 via Windows Update, WSUS, or manually download from Microsoft Update Catalog
  5. After patching, verify the installed build matches or exceeds the fixed version (e.g., Server 2019 should be 10.0.17763.7792 or higher)
  6. Restart the server if required by the update
  7. Confirm the RRAS service is running properly after restart
Caveat Standard Windows security update; minimal risk but test in staging environment before production deployment. Server 2008/2012 require full OS migration as they are end-of-life.

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
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
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,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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