dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2025-60705

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
Improper access control in Windows Client-Side Caching (CSC) Service 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 · high confidence

A local privilege escalation vulnerability exists in Windows Client-Side Caching (CSC) Service due to improper access control. An authorized attacker with local access can exploit this to gain elevated privileges on the affected system.

MitigationApply the Microsoft security update for CVE-2025-60705 via Windows Update or deploy the relevant patch through your organization's patch management infrastructure.

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
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 Windows version against affected ranges
    Run 'winver' or 'systeminfo | findstr /B /C:"OS"' to obtain the Windows version and build number, then compare against the affected version thresholds: Windows 10 1607 (build < 14393.8594), Windows 10 1809 (build < 17763.8027), Windows 10 21h2 (build < 19044.6575), Windows 10 22h2 (build < 19045.6575), Windows 11 23h2 (build < 22631.6199), Windows 11 24h2 (build < 26100.7092), Windows 11 25h2 (build < 26200.7092), or Windows Server 2008 R2 (all versions)
    Affected if The installed Windows version and build number fall within any of the affected ranges listed, or the system is Windows Server 2008 R2
  2. Verify CSC service presence
    Run 'sc queryex type= service state= all' and search for a service related to Client-Side Caching or Offline Files (commonly named 'CSC' or 'Offline Files'), or check the service via 'reg query "HKLM\SYSTEM\CurrentControlSet\Services" /s /v DisplayName' and look for entries containing 'Client-Side Caching' or 'Offline Files'
    Affected if A CSC or Offline Files service is installed on the system (this is required for the vulnerability to be exploitable)
  3. Check CSC service status
    If the CSC service is found, run 'sc query <service_name>' to determine if it is running, or check the service configuration via 'sc qc <service_name>' to see the startup type
    Affected if The CSC service exists and is either running or set to start automatically (start= auto or start= demand with current state running)

A user is affected if they are running any of the specified Windows versions within the affected build ranges (or Windows Server 2008 R2) AND the CSC/Offline Files service is present and enabled on the system.

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 the Microsoft security update for CVE-2025-60705 via Windows Update or deploy the relevant patch through your organization's patch management infrastructure.

Recommended fix High confidence

Install the May 2025 or later Windows Security Update (KBXXXXXX) for your specific Windows version from Windows Update or Microsoft Update Catalog

  1. Identify the current Windows version by running 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
  2. For Windows 10 1607, upgrade to version 10.0.14393.8594 or later
  3. For Windows 10 1809, upgrade to version 10.0.17763.8027 or later
  4. For Windows 10 21h2, upgrade to version 10.0.19044.6575 or later
  5. For Windows 10 22h2, upgrade to version 10.0.19045.6575 or later
  6. For Windows 11 23h2, upgrade to version 10.0.22631.6199 or later
  7. For Windows 11 24h2, upgrade to version 10.0.26100.7092 or later
  8. For Windows 11 25h2, upgrade to version 10.0.26200.7092 or later
Caveat Windows Server 2008 and Windows Server 2008 R2 are end-of-life with no patch available; migration to a supported OS required

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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