dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2025-60715

HIGH · 8.0 CVSS v3.1 Published 2025-11-11
Fix available
A fix is available. Upgrade to 10.0.14393.8594 / 10.0.17763.8027 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

Heap-based buffer overflow in Windows Routing and Remote Access Service (RRAS) allows an authorized attacker to execute arbitrary code remotely. The vulnerability stems from improper memory handling when processing network requests in RRAS, leading to heap corruption that can be exploited for code execution.

MitigationApply Microsoft security updates for CVE-2025-60715 to all affected Windows servers running RRAS, and restrict RRAS access to authorized personnel only while monitoring for indicators of compromise.

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 10 1607Operating system
Affected:< 10.0.14393.8594
Windows 10 1809Operating system
Affected:< 10.0.17763.8027
Windows 10 21h2Operating system
Affected:< 10.0.19044.6575
Windows 10 22h2Operating system
Affected:< 10.0.19045.6575
Windows 11 23h2Operating system
Affected:< 10.0.22631.6199
Windows 11 24h2Operating system
Affected:< 10.0.26100.7092
Windows 11 25h2Operating system
Affected:< 10.0.26200.7092
Windows Server 2008Operating system
Affected:all versions= r2

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 is installed on the system
    Open Server Manager > Add Roles and Features, or run 'Get-WindowsFeature RemoteAccess' in PowerShell on Windows Server. On Windows 10/11, check Services list for 'Routing and Remote Access' service status.
    Affected if RRAS is installed and the service exists on the system, placing it in the attack surface for this vulnerability
  2. Check if RRAS service is running or enabled
    Run 'Get-Service RemoteAccess' in PowerShell, or open Services.msc and look for 'Routing and Remote Access' service. Check if Status is Running or Startup type is set to Automatic/Manual.
    Affected if The RemoteAccess service is running or configured to start, making the vulnerable code path active
  3. Determine Windows version and build number
    Run 'winver' from Run dialog, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' in Command Prompt, or use 'Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion, OsHardwareAbstractionLayer' in PowerShell.
    Affected if The installed Windows version and build number fall within the affected ranges: Windows 10 1607 < 10.0.14393.8594, 1809 < 10.0.17763.8027, 21h2 < 10.0.19044.6575, 22h2 < 10.0.19045.6575; Windows 11 23h2 < 10.0.22631.6199, 24h2 < 10.0.26100.7092, 25h2 < 10.0.26200.7092; or Windows Server 2008/R2 of a
  4. Check for installed security update for CVE-2025-60715
    Open Control Panel > Programs and Features > View installed updates, or run 'Get-HotFix | Where-Object {$_.Description -like "Security Update"} | Sort-Object InstalledOn -Descending' in PowerShell. Search for the KB article listed in the Microsoft security bulletin for this CVE.
    Affected if No security update specific to CVE-2025-60715 is installed, leaving the RRAS vulnerability unpatched

A system is affected if it runs a vulnerable Windows version within the specified build ranges AND has RRAS installed with the RemoteAccess service enabled, and lacks the CVE-2025-60715 security update.

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.8594 / 10.0.17763.8027 / 10.0.19044.6575 or later
Fixed in 10.0.14393.859410.0.17763.802710.0.19044.6575
Interim mitigation

Apply Microsoft security updates for CVE-2025-60715 to all affected Windows servers running RRAS, and restrict RRAS access to authorized personnel only while monitoring for indicators of compromise.

Recommended fix High confidence

Apply the Microsoft security update for CVE-2025-60715 - install the KB corresponding to your Windows version (e.g., for Windows 10 22h2 install update bringing build to 10.0.19045.6575 or higher)

  1. Identify the current Windows version and build number by running 'winver' or 'systeminfo'
  2. Navigate to the Microsoft Security Response Center (msrc.microsoft.com) and search for CVE-2025-60715
  3. Download and install the corresponding security update for your Windows version from Microsoft Update Catalog or Windows Update
  4. Restart the affected system after applying the update
  5. Verify the update installed successfully by checking Windows Update history or running 'systeminfo' to confirm the build number matches or exceeds the fixed version for your product
  6. For Windows Server 2008/R2 systems: migrate to a supported Windows Server version as these OS versions are end-of-life and no longer receive security updates
Caveat Review application compatibility before patching; test RRAS configurations in staging if possible

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,840
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,144.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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