Skip to main content
CVE-2025-52541VulnerabilityPublished Updated

CVE-2025-52541: AMD Vivado™ Installation (Windows) · Uncontrolled Search Path Element

Affects AMD Vivado™ Installation (Windows)Source CVE Database V5

0

Not known to be exploited · CVSS 7.3 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
7.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
AMDVivado™ Installation (Windows)Affected–Fixed in–

AI-suggested

Organizations should implement the following mitigations: 1) Monitor AMD and Vivado vendor advisories closely and apply patches promptly once released. 2) Restrict local user permissions to the minimum necessary to reduce the risk of privilege escalation. 3) Employ application whitelisting and code integrity policies to prevent unauthorized DLLs from loading. 4) Use Windows security features such as Controlled Folder Access and Windows Defender Application Control to limit DLL loading from untrusted directories. 5) Educate users about the risks of running untrusted installers or tools and enforce strict operational procedures for software installation. 6) Regularly audit and monitor file system locations used by Vivado for DLLs to detect suspicious files. 7) Consider isolating Vivado installations in hardened virtual machines or containers to limit the blast radius of potential exploits. These steps go beyond generic advice by focusing on controlling DLL load paths, user permissions, and operational security specific to Vivado environments.

Description

A DLL hijacking vulnerability in Vivado could allow a local attacker to achieve privilege escalation, potentially resulting in arbitrary code execution.

References

Community reviews

Loading reviews…