EUVD-2025-210688
GHSA-qm95-8qpv-f995
Severity by source
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:A/VC:L/VI:L/VA:L/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Local attack requiring low-privilege credentials and a privileged user to trigger execution; AC:H reflects AT:P precondition; scope change and high C/I/A reflect arbitrary code execution outcome.
Primary rating from Vendor (amd).
CVSS VectorVendor: amd
Lifecycle Timeline
1DescriptionCVE.org
Weak permissions in the Vitis™ Unified installation path on local Windows machines could allow a low-privileged user to achieve privileged escalation, potentially resulting in arbitrary code execution.
AnalysisAI
Privilege escalation in AMD Vitis Unified on Windows enables a low-privileged local user to plant malicious code in the installation directory due to misconfigured filesystem permissions, potentially leading to arbitrary code execution under a more privileged context. Affected installations are the Vitis Unified Installer for FPGAs and Adaptive SoCs on Windows, patched in release 2026.1. No public exploit code and no active exploitation have been identified at time of analysis; CISA SSVC rates exploitation as none and the attack as non-automatable.
Technical ContextAI
AMD Vitis Unified is a development environment targeting FPGA and Adaptive SoC engineering workflows on Windows. The root cause is insecure directory ACLs on the Vitis installation path: Windows NTFS permissions are configured such that a standard low-privileged account retains write or modify rights over directories that should be restricted to administrators. This is a classic insecure file-permission vulnerability pattern - while no CWE is formally assigned, it aligns with CWE-732 (Incorrect Permission Assignment for Critical Resource) or CWE-427 (Uncontrolled Search Path Element). An attacker with local access can overwrite or plant binaries or DLLs in the installation tree. When a higher-privileged process subsequently loads those files, arbitrary code executes in the privileged context. The CVSS 4.0 vector (AV:L/AT:P/PR:L/UI:A) confirms local access with a specific attack precondition and a requirement that a privileged user actively interact with the tampered installation.
RemediationAI
Upgrade to Vitis Unified Installer 2026.1 or later, which is confirmed to contain the fix per EUVD-2025-210688 and AMD-SB-8015 (https://www.amd.com/en/resources/product-security/bulletin/AMD-SB-8015.html). Where immediate upgrade is not possible, administrators should manually audit and harden the ACLs on the Vitis installation directory tree using icacls or Group Policy, removing write and modify permissions for standard user accounts and restricting those rights to the SYSTEM account and the local Administrators group only - the trade-off is that some Vitis features requiring user-writable paths (license caches, temporary project files) may need to be redirected to per-user directories. On shared engineering workstations, consider restricting Vitis installation to dedicated, non-shared machines or applying application whitelisting (Windows Defender Application Control) to prevent unauthorized binaries from executing from the installation path.
Same weakness CWE-276 – Incorrect Default Permissions
View allSame technique Privilege Escalation
View allShare
External POC / Exploit Code
Leaving vuln.today