AMD Vitis Unified CVE-2025-48505

Exploitation requires: (1) local interactive or terminal access to a Windows machine with Vitis Unified installed; (2) a low-privileged but authenticated local or domain account on that machine; (3) the AT:P precondition from the CVSS 4.0 vector - a specific attack requirement not fully detailed in the public advisory, likely meaning a particular Vitis component or installation configuration must be present; and (4) active user interaction (UI:A) - a privileged user or process must execute a Vitis binary after the attacker has planted a malicious file. Exploitation is NOT possible remotely (AV:L rules out network-based attack). Exploitation is NOT possible by an unauthenticated user (PR:L). The attack is not automatable per SSVC. Single-user workstations where the sole user is the administrator are not meaningfully exposed because the attacker would already hold the highest privilege level.

Despite the description's mention of arbitrary code execution, the vendor-assigned CVSS 4.0 score of 1.0 is strikingly low and reflects significant mitigating factors embedded in the vector: AT:P (a specific attack precondition must be met) and UI:A (active user interaction - a privileged user must trigger execution of the modified binary) substantially limit practical exploitability. The SSVC assessment confirms exploitation is currently 'none' and the attack is not automatable, further reducing urgency. However, SSVC simultaneously rates Technical Impact as 'total', a signal that successful exploitation has severe consequences; this is consistent with arbitrary code execution and privilege escalation. The tension between a CVSS score of 1.0 and SSVC Technical Impact of 'total' should be noted: the score reflects difficulty of exploitation, not severity of outcome. No KEV listing and no public exploit code are confirmed. The vendor-reported VC:L/VI:L/VA:L impact metrics in the CVSS 4.0 vector appear to understate consequences relative to the 'arbitrary code execution' language in the description; defenders should treat this as a meaningful local privilege escalation risk on any shared or multi-tenant Windows engineering workstation running Vitis Unified. EPSS data is absent from the provided intelligence.

A low-privileged local user on a shared Windows engineering workstation identifies that the Vitis Unified installation directory grants write access to standard users. The attacker replaces or plants a malicious DLL or executable within the installation tree. When a developer or automated build agent with elevated privileges subsequently launches a Vitis tool, the planted code executes in the privileged context, achieving local privilege escalation to SYSTEM or administrator level. No public exploit code is confirmed at time of analysis, but the technique is a well-understood and widely-practiced local privilege escalation class.