CVE-2025-60710 Google Chronicle · YARA-L

Detect Microsoft Windows Link Following Vulnerability (CVE-2025-60710) in Google Chronicle

CVE-2025-60710 is an actively exploited Microsoft Windows link following vulnerability (CWE-59) that allows an attacker to abuse symbolic links or junction points to redirect file operations to unintended locations. This class of vulnerability is commonly leveraged for privilege escalation, file tampering, or unauthorized access to protected resources. The vulnerability is listed on CISA's Known Exploited Vulnerabilities catalog, indicating confirmed in-the-wild exploitation.

MITRE ATT&CK

Tactic
Privilege Escalation Defense Evasion Persistence

YARA-L Detection Query

Google Chronicle (YARA-L)
yaral
rule cve_2025_60710_link_following {
  meta:
    author = "df00tech"
    description = "Detects Windows link following exploitation activity associated with CVE-2025-60710"
    severity = "HIGH"
    priority = "HIGH"
    reference = "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-60710"

  events:
    $proc.metadata.event_type = "PROCESS_LAUNCH"
    $proc.principal.hostname = $host
    $proc.principal.user.userid != /(?i)(system|nt authority)/
    (
      re.regex($proc.target.process.command_line, `(?i)(mklink|junction|CreateSymbolicLink)`)
    )
    $file.metadata.event_type = "FILE_CREATION"
    $file.principal.hostname = $host
    (
      re.regex($file.target.file.full_path, `(?i)(\\Temp\\|AppData\\Local\\Temp\\|.+\.lnk$)`)
    )

  match:
    $host over 2m

  condition:
    $proc and $file
}
high severity medium confidence

Chronicle YARA-L rule for CVE-2025-60710 that correlates process launch events with suspicious command lines (mklink, junction) followed by file creation in temporary paths or .lnk files on the same host within 2 minutes.

Data Sources

Google ChronicleWindows Event Logs ingested via Chronicle forwarder

Required Tables

process_launchfile_creation

False Positives & Tuning

  • Build systems creating symlinks during compilation or artifact staging
  • Software distribution agents linking content libraries in temp directories
  • Forensic or endpoint management tools traversing file system paths

Other platforms for CVE-2025-60710


Testing Methodology

Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Create Symbolic Link in Temp Directory Targeting Privileged Path

    Expected signal: Sysmon Event ID 1 capturing mklink.exe execution with command line containing the symlink and target paths; Sysmon Event ID 11 showing creation of test_link.txt in C:\Windows\Temp\.

  2. Test 2Junction Point Creation Targeting System32

    Expected signal: Sysmon Event ID 1 with mklink /J command line and junction target; Windows Security Event ID 4663 on subsequent directory traversal through the junction.

  3. Test 3PowerShell Symbolic Link Creation via .NET API

    Expected signal: Sysmon Event ID 1 showing powershell.exe with CreateSymbolicLink in command line; Sysmon Event ID 11 or 12 for the created link object in Temp directory.

Unlock Pro Content

Get the full detection package for CVE-2025-60710 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections