dbcve.org
Windows Server 2008Operating system · Microsoft

CVE-2025-53720

HIGH · 8.0 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 →
84/100
Remediation priority · High
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
Heap-based buffer overflow in Windows Routing and Remote Access Service (RRAS) allows an authorized attacker to execute code 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 heap-based buffer overflow vulnerability exists in Windows Routing and Remote Access Service (RRAS) that allows an authenticated remote attacker to execute arbitrary code. The vulnerability stems from improper memory handling within the RRAS service, which processes network routing and remote access requests.

MitigationApply Microsoft security updates for CVE-2025-53720 to affected Windows servers running RRAS. If immediate patching is not feasible, disable RRAS if not required, or restrict network access to trusted authenticated users only.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

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 service status
    Open Services console (services.msc) or run 'Get-Service RemoteAccess' in PowerShell. Check if the RemoteAccess service is running or enabled.
    Affected if If RemoteAccess (RRAS) service is running or set to Automatic, the server is potentially affected.
  2. Identify Windows Server build version
    Run 'winver' from command prompt, or use PowerShell with '[System.Environment]::OSVersion.Version' or 'Get-ComputerInfo | Select-Object OsBuildNumber,OsVersion'. For more detail, run 'systeminfo' and look at the OS Version line.
    Affected if The build number displayed must be compared against the affected version thresholds.
  3. Compare build against affected versions
    For Windows Server 2016: compare to 10.0.14393.8330. For Server 2019: compare to 10.0.17763.7678. For Server 2022: compare to 10.0.20348.3989. For Server 2022 23h2: compare to 10.0.25398.1791. For Server 2025: compare to 10.0.26100.4851. Servers 2008/2012/2012 R2 are all affected regardless of build.
    Affected if If the installed build number is lower than the corresponding threshold for the server version, the system is affected.
  4. Confirm RRAS role is installed
    Open Server Manager, go to 'Add Roles and Features', or run 'Get-WindowsFeature -Name Routing' in PowerShell. Check if the Remote Access role with Routing role service is installed.
    Affected if If the Routing role is installed, the attack surface is present.

A server is affected if it runs a vulnerable Windows Server version (2016-2025 below threshold, or any 2008/2012) AND has the RRAS/RemoteAccess service enabled or installed.

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 CVE-2025-53720 to affected Windows servers running RRAS. If immediate patching is not feasible, disable RRAS if not required, or restrict network access to trusted authenticated users only.

Recommended fix High confidence

Apply the Microsoft security update for CVE-2025-53720; specific build numbers: Server 2016 at 10.0.14393.8330, Server 2019 at 10.0.17763.7678, Server 2022 at 10.0.20348.3989, Server 2022 23h2 at 10.0.25398.1791, Server 2025 at 10.0.26100.4851

  1. Identify the current build version of your Windows Server by running 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
  2. Apply the corresponding security update from Microsoft Update Catalog or Windows Update for your Windows Server version
  3. For Windows Server 2016: update to build 10.0.14393.8330 or later
  4. For Windows Server 2019: update to build 10.0.17763.7678 or later
  5. For Windows Server 2022: update to build 10.0.20348.3989 or later
  6. For Windows Server 2022 23h2: update to build 10.0.25398.1791 or later
  7. For Windows Server 2025: update to build 10.0.26100.4851 or later
  8. Restart the server if prompted by the update installation
Caveat Standard Microsoft security update; may require restart; ensure RRAS configuration is backed up before applying

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows Server 2008 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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