Cyber Resilience

CVE-2026-15684

Published
13 July 2026
Modified
14 July 2026
CVSS Score v3 7.3
Click a component to see what it means
Raw vectorCVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.0014 4th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2026-15684 is a high-severity Link Following (CWE-59) vulnerability in Zerodayinitiative (inferred from references). Its CVSS base score is 7.3 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 4th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Glarysoft Glary Utilities Link Following Local Privilege Escalation Vulnerability. This vulnerability allows local attackers to escalate privileges on affected installations of Glarysoft Glary Utilities. An attacker must first obtain the ability to execute low-privileged code on the target system in…

more

order to exploit this vulnerability. The specific flaw exists within the Disk Clean functionality. By creating a junction, an attacker can abuse the service to delete arbitrary files. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of SYSTEM. Was ZDI-CAN-27004.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
Why these techniques?

Local privilege escalation via junction (link following) abuse in Disk Clean service to delete arbitrary files and achieve SYSTEM code execution directly maps to Exploitation for Privilege Escalation.

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2025-63945Shared CWE-59
CVE-2026-2627Shared CWE-59
CVE-2025-15310Shared CWE-59
CVE-2026-49791Shared CWE-59
CVE-2026-33694Shared CWE-59
CVE-2026-39819Shared CWE-59
CVE-2026-11837Shared CWE-59
CVE-2026-4135Shared CWE-59
CVE-2026-50469Shared CWE-59
CVE-2025-49739Shared CWE-59

Affected Assets

Zerodayinitiative
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-10 Information Input Validation
  • AC-3 Access Enforcement
  • AC-6 Least Privilege
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V15.4.2

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly requires validation of file paths and link targets before the Disk Clean service performs privileged delete operations, blocking the junction-based arbitrary file deletion.

prevent

Enforces proper access checks on file operations so the high-privileged service cannot delete arbitrary files via attacker-controlled junctions.

prevent

Limits the Disk Clean service to the minimal privileges required, reducing the impact of any successful link-following abuse to SYSTEM.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require code to validate paths and avoid unsafe link following.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

detects

Security testing can detect link-following flaws before release.

prevents

Secure SDLC practices can mandate link-resolution checks and canonicalization before file access.

prevents

Application security requirements can explicitly require safe handling of symbolic links and path traversal.

prevents

Secure architecture principles include input validation and safe file-access design patterns.

prevents

Secure coding standards directly address canonicalization and symlink attacks during implementation.

none

Access-control rules can limit which files are reachable, reducing exposure to malicious links.

References