dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 27 Apr 2026.
Windows 11 24h2Operating system · Microsoft

CVE-2025-60710

HIGH · 7.8 CVSS v3.1 Published 2025-11-11
Fix available
A fix is available. Upgrade to 10.0.26100.7392 / 10.0.26200.7392 or later.
See remediation →
96/100
Remediation priority · Urgent
In the wild 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 Host Process for Windows Tasks 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

A link following vulnerability in the Host Process for Windows Tasks allows the application to access files through unsanitized symbolic links, enabling a locally authorized attacker to manipulate file access and elevate privileges to higher integrity levels.

MitigationApply the Microsoft security update for CVE-2025-60710 through Windows Update or enterprise patch management systems to remediate the link resolution flaw in the Host Process for Windows Tasks.

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 11 24h2Operating system
Affected:< 10.0.26100.7392
Windows 11 25h2Operating system
Affected:< 10.0.26200.7392
Windows Server 2025Operating system
Affected:< 10.0.26100.7392

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 'Get-ComputerInfo | Select WindowsVersion, OsVersion' in PowerShell to obtain the exact build number
    Affected if The Windows build number is less than 10.0.26100.7392 for version 24h2/Server 2025, or less than 10.0.26200.7392 for version 25h2
  2. Confirm Windows edition
    Run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to verify the exact Windows edition and version
    Affected if Running Windows 11 24h2, Windows 11 25h2, or Windows Server 2025 with a build number below the thresholds
  3. Identify the Windows Host Process for Windows Tasks
    Open Task Manager, go to the Details tab, and locate taskhostw.exe to confirm the process is running
    Affected if The taskhostw.exe process is present on an affected Windows version
  4. Verify local user access environment
    Review local user accounts and group memberships using 'net user' or 'Get-LocalUser' in PowerShell to determine if untrusted local users exist
    Affected if Untrusted or low-privilege local users have access to the system, enabling them to potentially exploit the link following flaw

A system is affected if it runs Windows 11 24h2, 25h2, or Windows Server 2025 with a build number below the specified thresholds and permits untrusted local user access.

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.26100.7392 / 10.0.26200.7392 or later
Fixed in 10.0.26100.739210.0.26200.7392
Interim mitigation

Apply the Microsoft security update for CVE-2025-60710 through Windows Update or enterprise patch management systems to remediate the link resolution flaw in the Host Process for Windows Tasks.

Recommended fix High confidence

Windows 11 24h2: build 10.0.26100.7392 or later | Windows 11 25h2: build 10.0.26200.7392 or later | Windows Server 2025: build 10.0.26100.7392 or later

  1. Open Settings on the Windows system
  2. Navigate to Windows Update (Settings > Windows Update)
  3. Click 'Check for updates' to download and install the latest security updates
  4. Ensure the update includes KB5053657 or later (the patch containing version 10.0.26100.7392 or 10.0.26200.7392)
  5. Restart the system when prompted to complete the installation
  6. Verify the installed version by running 'winver' command - should show build 26100.7392 or higher for 24h2/Server 2025, or 26200.7392 or higher for 25h2
Caveat Standard Windows cumulative security updates typically have no breaking changes; however, verify compatibility with critical line-of-business applications before deployment in production environments

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

Fix this in Windows 11 24h2 Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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