dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2025-60704

HIGH · 7.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 →
82/100
Remediation priority · High
Remotely reachable No privileges

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
Missing cryptographic step in Windows Kerberos allows an unauthorized attacker to elevate privileges 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

This vulnerability in Windows Kerberos involves a missing cryptographic step in the authentication protocol that allows an unauthorized attacker to elevate privileges over a network. The flaw likely permits bypassing proper authentication validation, enabling attackers to gain higher-level access within a Windows domain environment.

MitigationApply the Microsoft security update for CVE-2025-60704 to all affected Windows systems, particularly domain controllers and servers handling Kerberos authentication. Verify Kerberos functionality continues to operate correctly after patching.

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

CVSS:3.1/AV:N/AC:H/PR:N/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. Check Windows version number
    Open Command Prompt and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the installed Windows build number
    Affected if The displayed version falls within any of the affected ranges: 10.0.14393.x versions before 8594, 10.0.17763.x versions before 8027, 10.0.19044.x versions before 6575, 10.0.19045.x versions before 6575, 10.0.22631.x versions before 6199, 10.0.26100.x versions before 7092, or 10.0.26200.x versions be
  2. Verify Kerberos authentication is in use
    Check if the system is joined to an Active Directory domain by running 'systeminfo | findstr /C:"Domain"' or checking System Properties
    Affected if The system is joined to a Windows domain, meaning Kerberos is the default authentication protocol
  3. Identify if system is a domain controller or Kerberos server
    Run 'netdom query fsmo' or check Server Manager > Tools > Active Directory Users and Computers to see if the system holds a DC role
    Affected if The system is a Domain Controller or handles Kerberos ticket-granting operations for the domain

You are affected if your Windows version is below the fixed build numbers AND your system uses Kerberos authentication (domain-joined systems, especially domain controllers)

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-60704 to all affected Windows systems, particularly domain controllers and servers handling Kerberos authentication. Verify Kerberos functionality continues to operate correctly after patching.

Recommended fix High confidence

Install the appropriate Windows security update for your version (e.g., Windows 10 22h2 build 10.0.19045.6575 or later, Windows 11 23h2 build 10.0.22631.6199 or later)

  1. Identify the current Windows build version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which Windows version and build you are currently running
  3. For Windows 10 1607: Upgrade to build 10.0.14393.8594 or later
  4. For Windows 10 1809: Upgrade to build 10.0.17763.8027 or later
  5. For Windows 10 21h2: Upgrade to build 10.0.19044.6575 or later
  6. For Windows 10 22h2: Upgrade to build 10.0.19045.6575 or later
  7. For Windows 11 23h2: Upgrade to build 10.0.22631.6199 or later
  8. For Windows 11 24h2: Upgrade to build 10.0.26100.7092 or later
Caveat Windows Server 2008 R2 has reached end of support with no patch available; requires migration to a supported Windows Server version

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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