Vitis Unified EUVD-2025-210686

Exploitation requires all of the following: (1) a Windows machine where AMD Vitis Unified is installed, with at least one directory in the installation path writable by low-privileged accounts - this is the specific misconfiguration that defines the vulnerability; (2) the attacker must hold a low-privileged local Windows account on that machine (PR:L per CVSS vector); (3) a user with higher privileges must actively trigger execution of a Vitis component that traverses the writable path (UI:A per CVSS vector - exploitation cannot be automated without this interaction); and (4) attack preconditions must be met (AT:P), meaning the scenario is not straightforwardly exploitable against every default Vitis installation. Linux, macOS, or other non-Windows Vitis deployments are not indicated as affected. Remote exploitation is not possible; physical or remote-desktop access to the target machine is required.

The overall risk is low, consistent with the CVSS 4.0 base score of 1.0. All impact sub-scores are rated Low (VC:L/VI:L/VA:L/SC:L/SI:L), and subsequent-system availability impact is None (SA:N), indicating limited blast radius even in a successful exploitation scenario. The attack prerequisites (AT:P) and mandatory user interaction (UI:A) substantially narrow the exploitable population - the attacker cannot trigger execution autonomously and must rely on a privileged user performing a normal workflow action. No EPSS score and no KEV listing were provided, and no public exploit code has been identified, meaning real-world exploitation signals are entirely absent. The vulnerability is confined to developer workstations running a specialized FPGA toolchain on Windows, not servers or broadly networked infrastructure, which further constrains exposure. Even a small IT team managing a handful of engineering workstations would face minimal urgency here absent evidence of targeted exploitation, and the patch (Vitis SFD 2026.1) is already available. The primary residual concern is insider threat or a compromised low-privileged account on a shared development machine.

An attacker with a low-privileged Windows account on a shared Vitis development workstation identifies a directory within the Vitis Unified installation path that is writable by standard users. The attacker places a malicious DLL or executable in that directory, naming it to match a legitimate Vitis component. When an engineer or automated build process with higher privileges subsequently launches Vitis tooling and Windows resolves the binary search path, the malicious file is loaded and executes with the invoking process's privilege level. No public proof-of-concept has been identified at time of analysis.