AnyDesk CVE-2025-34499

Requires an interactive or local non-privileged account on a Windows host running AnyDesk 7.0.15 or 9.0.1, plus write permission to a directory that lies earlier in the service's unquoted binary path (e.g., C:\ or C:\Program Files\) so the attacker can drop a same-name executable like Program.exe. Exploitation also depends on the service being (re)started or the host rebooting to load the planted binary as SYSTEM. Limiting factors: no remote network reach despite the input vector's AV:N label, a pre-existing local foothold is mandatory, default directory ACLs on hardened systems may prevent writing the malicious file, and the affected AnyDesk versions must be installed.

This is a local privilege-escalation flaw (CWE-428, unquoted service path) in AnyDesk that lets a non-privileged local user obtain SYSTEM-level code execution. The signals conflict sharply: the supplied CVSS:4.0 vector asserts AV:N/PR:N/UI:N (remote, unauthenticated, no interaction), but the description explicitly states 'local non-privileged users' - the vector is almost certainly mislabeled and should be local with low privileges (a valid account on the host is required). Treat the AV:N as an error, not evidence of remote reach. EPSS is low (0.43%, 36th percentile) and the CVE is NOT on CISA KEV, so there is no indication of widespread or active exploitation. However, publicly available exploit code exists (Exploit-DB 51968 and 52258), lowering the skill barrier. Net: this is a credible local post-compromise escalation primitive rather than an internet-facing emergency - real priority on multi-user or already-breached Windows hosts running the affected AnyDesk builds, but not a drop-everything remote RCE despite the misleading network vector. No SSVC decision data was provided in the input.

An attacker who already has an unprivileged foothold on a Windows host (via phishing, a low-priv account, or malware) plants a malicious executable such as C:\Program.exe in a directory along AnyDesk's unquoted service path. When the service restarts or the machine reboots, Windows launches the attacker's binary as SYSTEM instead of the intended AnyDesk executable. Public proof-of-concept exploit code exists (Exploit-DB 51968 and 52258), so weaponization requires little effort.