CVE-2025-60710: Windows link-following privilege escalation

Quick Answer

CVE-2025-60710 affects Host Process for Windows Tasks: an authorized local attacker can exploit improper link resolution to gain SYSTEM privileges. Microsoft reissued the fix in December 2025 to address it comprehensively, so November-only patch evidence is insufficient. Match Windows 11 24H2/25H2 or Server 2025 to the revised update rows, preserve endpoint evidence and retain the distinction between patching and investigation of CISA's known ransomware use.

Evidence check: The vendor evidence and its limits are described below. CISA KEV catalog 2026.10.02 was checked October 2; catalog chronology is separate from vendor publication history and evidence of compromise in your deployment. No exploit or update test is claimed.

Context

Status At A Glance

Product scope	Microsoft — Windows
CVE	CVE-2025-60710
TechGeeks response tier	P0 — confirm an exact match and act now
CISA KEV added	2026-04-13
Vendor severity	Important (Microsoft).
CVSS	7.8 (Microsoft CVSS v3.1 base; local, low privileges required).
Ransomware field	Known — CISA currently associates this CVE with known ransomware-campaign use.
Forensic-triage field	No in the current CISA field; organizations should still investigate when exposure or evidence warrants it.
CWE	CWE-59
Federal remediation date	2026-04-27 — applies to covered federal agencies; other organizations should set a risk-based deadline.

What Happened

Host Process for Windows Tasks link resolution: Microsoft describes a local privilege-escalation path to SYSTEM. CISA confirms exploitation and records ransomware use; those signals do not show its prevalence or establish compromise of a particular Windows host.

Affected Scope

Windows releases and servicing levels identified in the live MSRC advisory; exact applicability must be matched by product and build.

Match the exact edition, hardware or virtual platform, release, patch level, enabled feature, and management exposure. A product-family name alone is not enough to establish applicability.

Steps

What To Do Now

1. Confirm. Inventory every Windows asset and record its exact version, patch level, role, relevant configuration, and exposure.
2. Preserve. Save UTC timestamps, off-device authentication, firewall, proxy, DNS, endpoint, application, and SIEM evidence before logs rotate or a disruptive change removes context.
3. Contain. Restrict unnecessary internet and management-plane access using supported controls. Follow the live advisory: Open the live Microsoft advisory.
4. Remediate. Install the applicable Microsoft security update and verify the resulting Windows build against the live MSRC table.
5. Validate. Verify the resulting version or patch level, service health, logging, expected access, an expected denial, and representative dependent workflows.
6. Escalate. If exposure overlapped the vulnerable period or evidence is suspicious, treat the system as a potential incident and follow vendor and incident-response recovery guidance.

Fixed Releases And Mitigation

Investigation And Recovery

CISA lists the vulnerability as known exploited and flags known ransomware-campaign use. Review endpoint telemetry for suspicious link-following behavior followed by privilege escalation.

When an attacker may have gained administrative, root, SYSTEM, identity, management-plane, or code-execution access, patching alone is not an eradication claim. Preserve evidence, scope affected accounts and downstream systems, rotate exposed credentials or certificates when justified, and rebuild from a trusted source when vendor or incident-response guidance requires it.

Notes

Exploitation Evidence

Vendor statement: The checked Microsoft CVRF still records Exploited: No in its publication-era assessment. CISA later added this CVE on April 13, 2026 and records known ransomware use. The older Microsoft field must not be presented as a current denial of exploitation.

CISA statement: CVE-2025-60710 was added to KEV on 2026-04-13. The ransomware field is Known, and the forensic-triage field is No. These are separate signals.

Validation And Boundaries

This notice does not prove that every product carrying the family name is affected, that exploitation is widespread, that a clean indicator search rules out compromise, or that a successful update restored trust. TechGeeks has not reproduced the exploit and does not replace the vendor advisory, asset inventory, vulnerability scanner, or incident-response process.

Related TechGeeks Resources

• TechGeeks Security Notice Center
• All Security Notices
• What to Do When a Device Hits CISA KEV
• Router CVE Exposure, Version, and Mitigation Checklist
• IoT Firmware Update and End-of-Support Checklist
• Live Protect and Runtime Vulnerability Shielding

References

• Microsoft security advisory
• NVD CVE record
• CISA source

Wrap-Up

Record whether CVE-2025-60710 applies to your environment. If it does, assign an owner, preserve the change and investigation evidence, complete the vendor action, and document the validated result.

Correction policy: If a primary source changes affected versions, remediation, exploitation status, or recovery guidance, TechGeeks will update this page and its verification date.