CVE-2025-60710: Host Process for Windows Tasks Elevation of Privilege Vulnerability
Improper link resolution before file access ('link following') in Host Process for Windows Tasks allows an authorized attacker to elevate privileges locally.
Security readout for executives and security teams
Plain-English summary
A logged-in attacker with limited Windows privileges can exploit unsafe handling of file links to gain elevated rights. Successful exploitation could expose sensitive data, alter systems, or disrupt operations. Because CISA lists this vulnerability as known exploited, affected Windows endpoints and servers require urgent attention.
Executive priority
Treat this as an urgent patching priority because exploitation is documented and successful use can provide full elevated control. Focus first on high-value servers and broadly accessible endpoints. Track coverage, reboot completion, validation results, and formally managed exceptions until the affected estate is remediated.
Technical view
CVE-2025-60710 is a CWE-59 link-following flaw in Host Process for Windows Tasks. It requires local access and low privileges, needs no user interaction, and has low attack complexity. The CVSS 3.1 score is 7.8, with potentially high confidentiality, integrity, and availability impact.
Likely exposure
The bundle identifies Windows 11 24H2 build 10.0.26100.0, Windows 11 25H2 build 10.0.26200.0, and Windows Server 2025 build 10.0.26100.0, including Server Core. Exposure requires an attacker to already have authorized local access or equivalent low-privileged execution.
Exploitation context
CISA KEV status supports active exploitation in the wild. The supplied evidence does not describe exploitation scale, targeted sectors, observed indicators, or attack chains. This is a local privilege-escalation vulnerability, so attackers generally need an initial foothold before using it.
Researcher notes
The bundle establishes local, low-privilege, low-complexity exploitation without user interaction, but provides no technical root-cause detail beyond improper link resolution. It also supplies no exploit chain, indicators, affected component paths, or exact fixed build information. Researchers should obtain those details from Microsoft before designing detection or validation logic.
Mitigation direction
Inventory the listed Windows releases and compare installed builds and updates against Microsoft guidance.
Apply the applicable Microsoft security update using established accelerated patch procedures.
Prioritize exposed servers, privileged workstations, and endpoints where untrusted users can execute code.
Consult Microsoft guidance for supported remediation when immediate updating is operationally impossible.
Validation and detection
Confirm affected asset versions and editions through endpoint or vulnerability-management inventory.
Verify the applicable Microsoft security update is installed and survives reboot.
Rescan updated systems and reconcile exceptions against Microsoft advisory information.
Review endpoint telemetry for unexplained privilege elevation; the bundle provides no specific indicators.
Use controlled, authorized regression testing to confirm low-privileged users cannot gain elevated rights.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-59: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
Exploitation: activeAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-59 · source CWE mapping
Improper Link Resolution Before File Access ('Link Following')
Improper Link Resolution Before File Access ('Link Following') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.