Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2025-60710: Windows Task Host Link-Following Privilege Escalation

Published Nov 11, 2025 · Updated 11 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days3 mentions · peak 3 in a dayToday
CVSS7.8High · v3.1
EPSS4.6%92nd percentile
CISA KEVYesAdded Apr 13, 2026
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2025-60710CWE-59 · Improper Link Resolution Before…

CVE-2025-60710 is an improper link resolution vulnerability in Host Process for Windows Tasks affecting Windows 11 and Windows Server 2025. A Windows AI Recall scheduled task executing as SYSTEM performs deletion operations in a user-writable directory without properly validating junctions or symbolic links. An authorized local attacker can redirect these privileged operations to attacker-selected protected files. The resulting file-deletion primitive can be leveraged to achieve SYSTEM-level code execution. CISA added the vulnerability to its Known Exploited Vulnerabilities catalog in April 2026 and confirmed ransomware campaign use in August 2026.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a local attacker with basic user permissions to gain SYSTEM privileges and take full control of the affected device, with high confidentiality, integrity, and availability impact. Privileged file deletion can damage protected system resources, while subsequent SYSTEM-level execution can enable credential theft, security-tool tampering, persistence, and ransomware deployment. The compromised endpoint can also support lateral movement, subject to available credentials and network access.

Mitigation

If you can’t patch tonight, do this now.

If updates cannot be installed immediately, Microsoft advises customers running Windows Server 2025 with Desktop Experience to disable the Task Scheduler task \Microsoft\Windows\WindowsAI\Recall\PolicyConfiguration. Reenable the task only after installing the security update. This workaround is specifically documented for that server configuration; an equivalent workaround for Windows 11 is not specified.

Remediation

Patch, then assume compromise.

Install the December 2025 Microsoft security updates or later cumulative updates that include the complete fix. Microsoft states that the December updates comprehensively address CVE-2025-60710 for all supported editions of Windows 11 Version 24H2, Windows 11 Version 25H2, and Windows Server 2025. Do not rely solely on the initial November 2025 fix. Systems configured for automatic updates require no further action once the applicable updates are installed.

Public exploits

Exploits

2 exploits validated by Mallory's analysis.

View more in app →
CVE-2025-60710This repository contains a proof-of-concept (PoC) exploit for CVE-2025-60710, a local privilege escalation vulnerability in Microsoft Windows. The exploit targets the scheduled task \Microsoft\Windows\WindowsAI\Recall\PolicyConfiguration, which, when triggered, causes the system to delete directories in the user's %LOCALAPPDATA% without proper symlink checks. The exploit is implemented in C++ and consists of several source and header files, with the main logic in 'main.cpp' and 'FileOrFolderDelete.cpp'. The exploit works in two stages: first, it prepares the environment by creating a directory structure and setting up symbolic/junction links. The user is prompted to trigger the vulnerable delete operation (e.g., by starting the scheduled task). After the delete is triggered, the exploit resumes and leverages the SYSTEM context to perform privileged file operations, such as dropping a malicious DLL or manipulating rollback files via MSI installer tricks. The exploit uses Windows APIs for file operations, directory monitoring, and privilege escalation techniques based on file system manipulation. Key fingerprintable endpoints include the user's CoreAIPlatform.00\UKP directory, C:\Config.Msi, and HID.DLL in the Common Files directory. The exploit also interacts with the Windows registry to check for installer folder registration. The repository is structured as a Visual Studio C++ project, with resource files for embedded payloads (MSI, RBS, RBF). The README provides a technical overview and usage instructions, confirming the exploit's purpose and capabilities.Wh04m1001 · Disclosed Nov 11, 2025 · cpp · localPoCCVE-2025-60710This repository contains a proof-of-concept (PoC) exploit for CVE-2025-60710, a local privilege escalation vulnerability in Microsoft Windows. The exploit targets the scheduled task \Microsoft\Windows\WindowsAI\Recall\PolicyConfiguration, which, when triggered, causes the system to delete directories in the user's %LOCALAPPDATA% without proper symlink checks. The exploit is implemented in C++ and consists of several source and header files, with the main logic in 'main.cpp' and 'FileOrFolderDelete.cpp'. The exploit works in two stages: first, it prepares the environment by creating a directory structure and setting up symbolic/junction links. The user is prompted to trigger the vulnerable delete operation (e.g., by starting the scheduled task). After the delete is triggered, the exploit resumes and leverages the SYSTEM context to perform privileged file operations, such as dropping a malicious DLL or manipulating rollback files via MSI installer tricks. The exploit uses Windows APIs for file operations, directory monitoring, and privilege escalation techniques based on file system manipulation. Key fingerprintable endpoints include the user's CoreAIPlatform.00\UKP directory, C:\Config.Msi, and HID.DLL in the Common Files directory. The exploit also interacts with the Windows registry to check for installer folder registration. The repository is structured as a Visual Studio C++ project, with resource files for embedded payloads (MSI, RBS, RBF). The README provides a technical overview and usage instructions, confirming the exploit's purpose and capabilities.redpack-kr · Disclosed Nov 12, 2025 · cpp · localPoC
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows 11 24h2operating_system
Microsoft CorporationWindows 11 25h2operating_system
Microsoft CorporationWindows Server 2025operating_system
FAQ

Frequently asked questions

Is CVE-2025-60710 exploited in the wild?
Yes. As of Nov 10, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Apr 13, 2026.
Is there a public exploit for CVE-2025-60710?
Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2025-60710, the earliest disclosed Nov 11, 2025.
Is there a patch for CVE-2025-60710?
Install the December 2025 Microsoft security updates or later cumulative updates that include the complete fix. Microsoft states that the December updates comprehensively address CVE-2025-60710 for all supported editions of Windows 11 Version 24H2, Windows 11 Version 25H2, and Windows Server 2025.
What products are affected by CVE-2025-60710?
Microsoft Corporation Windows Server 2025, Microsoft Corporation Windows 11 24h2, and Microsoft Corporation Windows 11 25h2.
How severe is CVE-2025-60710?
CVE-2025-60710 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 4.6% (92nd percentile) as of Nov 10, 2026.
Activity feed

Recent activity

40 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+8 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity23Community discussion across Reddit, Mastodon, and other social sources.