dbcve.org
Windows Server 2008Operating system · Microsoft

CVE-2025-53796

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

Buffer over-read vulnerability in Windows Routing and Remote Access Service (RRAS) allows an unauthenticated remote attacker to read memory contents beyond allocated buffers, potentially exposing sensitive information from the affected system's memory.

MitigationApply the relevant Microsoft security update for this vulnerability through standard Windows patch management processes; verify RRAS is only enabled on systems where it is 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 is installed and running
    Open Services console (services.msc) and look for 'Routing and Remote Access' service, or run 'Get-Service RemoteAccess' in PowerShell. Also check Server Manager under 'Add Roles and Features' to see if 'Remote Access' role is installed.
    Affected if The RRAS service is installed and enabled on the system. If RRAS is not present, the vulnerability cannot be exploited.
  2. Check Windows Server version and build number
    Run 'winver' from command prompt or 'systeminfo' to obtain the full OS version and build number (for example, 10.0.17763.XXXX). Alternatively, run 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild' in command prompt.
    Affected if The detected build number falls below the fixed version for your specific Windows Server release.
  3. Compare installed version against affected ranges
    Cross-reference your detected build number with the following thresholds: 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. Server 2008 and 2012 are fully affected regardless of build.
    Affected if Your Windows Server version and build number is lower than the fixed version for your specific release, and RRAS is enabled.
  4. Confirm RRAS is exposed to network
    Check RRAS configuration in Routing and Remote Access snap-in (rrasmgmt.msc) or via 'netsh routing ip show config' to see if the server is accepting remote connections. Also verify firewall rules allowing inbound traffic to RRAS ports (default PPTP/L2TP/IKE2).
    Affected if RRAS is configured to accept remote connections and is reachable from the network, enabling unauthenticated remote exploitation.

You are affected if RRAS (Routing and Remote Access) is enabled on a Windows Server version that falls below the fixed build number for your release, making the server exploitable by remote unauthenticated attackers.

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 relevant Microsoft security update for this vulnerability through standard Windows patch management processes; verify RRAS is only enabled on systems where it is required.

Recommended fix High confidence

Windows Server 2016: 10.0.14393.8422 or later | Windows Server 2019: 10.0.17763.7792 or later | Windows Server 2022: 10.0.20348.4106 or later | Windows Server 2022 23h2: 10.0.25398.1849 or later | Windows Server 2025: 10.0.26100.6508 or later

  1. Identify the current Windows Server version by running 'winver' or 'systeminfo' in Command Prompt
  2. Open Windows Update by running 'ms-settings:windowsupdate' or using Server Manager > Local Server > Windows Update
  3. Check for and install all available security updates, specifically looking for updates that address this CVE (may be labeled as Windows RRAS security update)
  4. After installation, restart the server to apply the changes
  5. Verify the fix by checking the OS build number matches or exceeds the fixed version for your Windows Server edition
Caveat Standard security update - minimal risk; requires server restart to apply patch; test in 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 / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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