# CVE-2025-60710: Microsoft Windows Link Following

> An authorized local attacker can elevate privileges via improper link resolution in the Host Process for Windows Tasks.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Yes, since 13 Apr 2026 (CISA KEV), used in ransomware
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Nov 2025
- **Updated:** 15 Aug 2026
- **Also known as:** GHSA-wmgf-g9pc-mvh3

## What is CVE-2025-60710?

CVE-2025-60710 is a high-severity path traversal vulnerability in Microsoft Windows 11 24h2, published on 11 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper link resolution before file access ('link following') in Host Process for Windows Tasks allows an authorized attacker to elevate privileges locally.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2025-60710?

It affects 3 products.


Products: Microsoft Windows 11 24h2, Microsoft Windows 11 25h2, Microsoft Windows Server 2025.

## How do I fix CVE-2025-60710?

No fix has been published for CVE-2025-60710 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 27 Apr 2026.

## Is CVE-2025-60710 being exploited?

Yes. Attackers have exploited CVE-2025-60710 in the wild since at least 13 Apr 2026, including in ransomware campaigns.

Public exploit code:

- https://github.com/redpack-kr/CVE-2025-60710 (github_poc): https://github.com/redpack-kr/CVE-2025-60710
- https://github.com/Wh04m1001/CVE-2025-60710 (github_poc): https://github.com/Wh04m1001/CVE-2025-60710

## Other vulnerabilities in Microsoft Windows 11 24h2

- [CVE-2026-54990](https://insights.sbomify.com/CVE-2026-54990/): Remote Desktop Client Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2025-50165](https://insights.sbomify.com/CVE-2025-50165/): Windows Graphics Component Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2025-21311](https://insights.sbomify.com/CVE-2025-21311/): Windows NTLM V1 Elevation of Privilege Vulnerability (critical 9.8)
- [CVE-2026-108463](https://insights.sbomify.com/CVE-2026-108463/): Windows SmartScreen Security Feature Bypass Vulnerability (high 8.8)
- [CVE-2026-83523](https://insights.sbomify.com/CVE-2026-83523/): Windows Image Acquisition Remote Code Execution Vulnerability (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-60710 and fix it if it is affected.

What it is: CVE-2025-60710 is a high-severity path traversal vulnerability in Microsoft Windows 11 24h2, published on 11 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-60710 in the wild since at least 13 Apr 2026, including in ransomware campaigns.

Affected product: Microsoft Windows 11 24h2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-60710/ (Markdown: https://insights.sbomify.com/CVE-2025-60710/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-60710
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-60710
- OSV: https://osv.dev/vulnerability/CVE-2025-60710

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-60710/
Summaries are generated and may contain mistakes; the official description above is the record.