dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2025-59510

MEDIUM · 5.5 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 →
57/100
Remediation priority · Elevated
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
Improper link resolution before file access ('link following') in Windows Routing and Remote Access Service (RRAS) allows an authorized attacker to deny service 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

A link following vulnerability in Windows Routing and Remote Access Service (RRAS) allows a local, authorized attacker to cause a denial of service by exploiting improper symbolic link resolution before file access. The attacker with local access can manipulate symbolic links to trigger service disruption.

MitigationApply Microsoft security updates for Windows RRAS when available; restrict local access to authorized personnel only 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 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 2012Operating system
Affected:= 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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
    Open Services console (services.msc) and look for 'Routing and Remote Access' service, or run 'Get-Service RemoteAccess' in PowerShell
    Affected if RRAS service is present and running on the system
  2. Check Windows version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify the exact Windows build number
    Affected if Windows build number is lower than any of these thresholds: 14393.8594 (Win10 1607), 17763.8027 (Win10 1809), 19044.6575 (Win10 21h2), 19045.6575 (Win10 22h2), 22631.6199 (Win11 23h2), 26100.7092 (Win11 24h2), 26200.7092 (Win11 25h2), or Server 2012 R2 (any version)
  3. Confirm update installation status
    Run 'Get-HotFix | Where-Object {$_.Description -eq "Security Update"}' and check for the specific KB for this CVE, or view Windows Update history in Settings > Windows Update > Update history
    Affected if No corresponding security update for this CVE has been installed and the Windows version falls within the affected range

System is affected if RRAS is installed and the Windows build number is below the fixed version thresholds listed for your Windows release.

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 Windows RRAS when available; restrict local access to authorized personnel only to reduce attack surface.

Recommended fix High confidence

Windows Security Update (specific build per version family - see steps 4-11)

  1. 1. Identify the current Windows version and build number by running 'winver' or 'systeminfo' in Command Prompt
  2. 2. Determine which Windows version family your system belongs to (e.g., Windows 10 22h2, Windows 11 23h2, etc.)
  3. 3. Apply the appropriate Windows Security Update that addresses CVE-2025-59510
  4. 4. For Windows 10 1607 systems, install update reaching build 10.0.14393.8594 or later
  5. 5. For Windows 10 1809 systems, install update reaching build 10.0.17763.8027 or later
  6. 6. For Windows 10 21h2 systems, install update reaching build 10.0.19044.6575 or later
  7. 7. For Windows 10 22h2 systems, install update reaching build 10.0.19045.6575 or later
  8. 8. For Windows 11 23h2 systems, install update reaching build 10.0.22631.6199 or later
Caveat Standard Windows update risks apply - ensure backup of critical data and test 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
  • 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-59510 — 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-59510 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