dbcve.org
Windows Server 2016Operating system · Microsoft

CVE-2025-60713

HIGH · 7.8 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 →
80/100
Remediation priority · High
Zero-click

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
Untrusted pointer dereference in Windows Routing and Remote Access Service (RRAS) allows an authorized attacker to elevate privileges locally.

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

An untrusted pointer dereference vulnerability exists in Windows Routing and Remote Access Service (RRAS). This memory safety flaw allows a locally authorized attacker to manipulate pointer references in a way that leads to privilege escalation from their current authorized level to higher system privileges.

MitigationApply the Microsoft security update for CVE-2025-60713 when released. If RRAS is not required, disable the service to reduce attack surface. Prioritize patching on systems where local untrusted users have access.

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 2016Operating system
Affected:< 10.0.14393.8594
Windows Server 2019Operating system
Affected:< 10.0.17763.8027
Windows Server 2022Operating system
Affected:< 10.0.20348.4346
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1965
Windows Server 2025Operating system
Affected:< 10.0.26100.7092

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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. Check if RRAS service is installed
    Open Services (services.msc) and look for 'Routing and Remote Access' service, or run: Get-Service -Name RemoteAccess in PowerShell
    Affected if The RRAS service exists on the system (even if stopped, the vulnerable code is present)
  2. Check Windows version
    Run 'winver' or in PowerShell: [System.Environment]::OSVersion.Version.ToString()
    Affected if Version is below 10.0.14393.8594 (Server 2016), 10.0.17763.8027 (Server 2019), 10.0.20348.4346 (Server 2022), 10.0.25398.1965 (Server 2022 23h2), or 10.0.26100.7092 (Server 2025)
  3. Check if RRAS is enabled
    Run 'netsh routing ip show global' or check via Server Manager under 'Add Roles and Features' > 'Remote Access' role
    Affected if RRAS role or feature is installed and enabled on the server
  4. Check RRAS service status
    Run: Get-Service -Name RemoteAccess | Select-Object Status, StartType
    Affected if Service is in Running state, indicating the vulnerable code path is active

System is affected if RRAS is installed and the Windows Server version is below the specified build numbers for each supported version line.

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.20348.4346 or later
Fixed in 10.0.14393.859410.0.17763.802710.0.20348.4346
Interim mitigation

Apply the Microsoft security update for CVE-2025-60713 when released. If RRAS is not required, disable the service to reduce attack surface. Prioritize patching on systems where local untrusted users have access.

Recommended fix High confidence

Windows Server 2016: 10.0.14393.8594 | Windows Server 2019: 10.0.17763.8027 | Windows Server 2022: 10.0.20348.4346 | Windows Server 2022 23h2: 10.0.25398.1965 | Windows Server 2025: 10.0.26100.7092

  1. Identify the current Windows Server version by running 'winver' or 'systeminfo' in Command Prompt
  2. Confirm if the Routing and Remote Access Service (RRAS) role is installed by running 'Get-WindowsFeature -Name Routing' in PowerShell (Server Manager modules)
  3. Apply the appropriate Windows cumulative/security update for your specific Windows Server version from Microsoft Update Catalog or WSUS
  4. Restart the server as required after the update installation
  5. Verify the patch was applied successfully by checking the installed updates list or running 'winver' to confirm the version matches or exceeds the fixed version for your release
Caveat Standard Windows cumulative updates - may require reboot and should be tested in staging environment first

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

Fix this in Windows Server 2016 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
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,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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