Skip to main content

Vitis Unified EUVDEUVD-2025-210686

| CVE-2025-61970 LOW
Incorrect Default Permissions (CWE-276)
2026-08-11 psirt@amd.com GHSA-6rv5-3vh8-6642
1.0
CVSS 4.0 · Vendor: amd

Severity by source

Vendor (amd) PRIMARY
1.0 LOW
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
vuln.today AI
4.2 MEDIUM

Local access, low privilege, required user interaction, and the specific writable-path precondition justify AC:H; limited CIA impact reflects binary hijacking scope without scope change.

3.1 AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L
4.0 AV:L/AC:L/AT:P/PR:L/UI:A/VC:L/VI:L/VA:L/SC:L/SI:L/SA:N

Primary rating from Vendor (amd).

CVSS VectorVendor: amd

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
A
Scope
X

Lifecycle Timeline

1
Analysis Generated
Aug 11, 2026 - 23:41 vuln.today

DescriptionCVE.org

Weak permissions in the Vitis™ Unified installation path on local Windows machines could allow a low-privileged user to create arbitrary code, potentially resulting in binary hijacking.

AnalysisAI

Binary hijacking is possible on Windows machines running AMD Vitis Unified due to weak filesystem permissions on the installation directory. A low-privileged local user can write arbitrary executables into paths traversed by higher-privileged processes, causing those processes to load attacker-controlled code when triggered by an interactive user. The CVSS 4.0 score of 1.0 reflects significant limiting prerequisites: local access, low-privilege credentials, specific attack preconditions, and required user interaction are all mandatory for exploitation. No public exploit has been identified at time of analysis.

Technical ContextAI

AMD Vitis Unified is a software development platform targeting FPGA, embedded processor, and adaptive compute workloads, primarily used by hardware engineers on Windows workstations. The vulnerability class is binary (DLL or executable) hijacking: Windows resolves library and executable paths by searching a sequence of directories, and if any directory in that sequence is writable by a low-privileged account, an attacker can plant a malicious file that a higher-privileged process loads instead of the legitimate one. The root cause is misconfigured Access Control Lists (ACLs) on the Vitis installation directory, allowing write access to accounts that should only have read/execute permissions. Although CWE is listed as N/A in the source data, this pattern is most closely associated with CWE-732 (Incorrect Permission Assignment for Critical Resource) and CWE-426 (Untrusted Search Path). The CVSS 4.0 vector confirms local attack surface (AV:L), attack preconditions (AT:P), low privilege required (PR:L), and active user interaction (UI:A), consistent with a hijacking scenario requiring a privileged user to invoke the affected binary.

RemediationAI

The primary fix is to apply the Vitis™ Embedded Single File Download (SFD) for Windows patch version 2026.1, as documented in AMD Security Bulletin AMD-SB-8015 (https://www.amd.com/en/resources/product-security/bulletin/AMD-SB-8015.html). For environments where immediate patching is not feasible, administrators should audit and tighten ACLs on the Vitis Unified installation directory using icacls or Group Policy, removing write permissions for standard user accounts and retaining only read and execute access. This compensating control eliminates the writable path condition that makes hijacking possible, though it may interfere with Vitis features that legitimately write to the installation directory during operation or updates - verify with AMD documentation before applying. Additionally, restricting local login access to development machines to only authorized engineering personnel reduces the pool of potential attackers. Patch version 2026.1 is confirmed by ENISA EUVD data; no earlier partial-fix version is noted.

Share

EUVD-2025-210686 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy