dbcve.org
Windows Server 2008Operating system · Microsoft

CVE-2025-53719

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 · high confidence

This is an information disclosure vulnerability in Windows Routing and Remote Access Service (RRAS) where an uninitialized resource is used, allowing an authorized attacker to potentially read sensitive information from memory over a network. The vulnerability stems from improper initialization of data structures within the RRAS component.

MitigationApply Microsoft security updates for this vulnerability to affected Windows servers running RRAS. If RRAS is not required, consider disabling the service to reduce attack surface.

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. Check if RRAS service is installed
    Run 'Get-Service -Name RemoteAccess' in PowerShell or check registry key 'HKLM\SYSTEM\CurrentControlSet\Services\RemoteAccess'
    Affected if The RemoteAccess service does not exist or is not present on the system
  2. Check RRAS service status
    Run 'Get-Service -Name RemoteAccess' to see if the service is Running or Stopped
    Affected if The RemoteAccess service is in a Running state - the vulnerability only applies when RRAS is active
  3. Determine Windows Server version
    Run 'winver' or execute 'Get-ItemProperty -Path 'HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion' | Select-Object CurrentBuild, DisplayVersion, UBR' in PowerShell
    Affected if The build number falls below the following thresholds: Server 2016 < 14393.8330, Server 2019 < 17763.7678, Server 2022 < 20348.3989, Server 2022 23h2 < 25398.1791, Server 2025 < 26100.4851
  4. Confirm Windows Server 2008/2012 installation
    Run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify the exact Windows version
    Affected if The system is running Windows Server 2008 (any version/R2) or Windows Server 2012 (any version/R2) - all of these versions are affected

A system is affected if RRAS is enabled/running AND the Windows Server version matches one of the affected version ranges listed in the CVE (any version for Server 2008/2012, or below the specified build numbers for newer versions).

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 Microsoft security updates for this vulnerability to affected Windows servers running RRAS. If RRAS is not required, consider disabling the service to reduce attack surface.

Recommended fix High confidence

Apply security updates: Windows Server 2016 to build 10.0.14393.8330 or later; Windows Server 2019 to build 10.0.17763.7678 or later; Windows Server 2022 to build 10.0.20348.3989 or later; Windows Server 2022 23h2 to build 10.0.25398.1791 or later; Windows Server 2025 to build 10.0.26100.4851 or lat

  1. Open Windows Update on the affected server (Start > Settings > Update & Security > Windows Update)
  2. Click 'Check for updates' to identify available security updates
  3. Install the latest cumulative security update for your Windows Server version
  4. Restart the server if prompted after installation
  5. Verify the update was installed successfully by checking Windows Update history
  6. For Windows Server 2008/2012 which are out of mainstream support, check if Extended Security Updates (ESU) are applicable or consider migrating to a supported version
Caveat Windows Server 2008 and 2012 are end-of-life; no official patches available; consider migration to supported version

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