Skip to main content
CVE-2025-54519VulnerabilityPublished

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

Affects AMD Vivado™ Documentation Navigator 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 3% 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 12 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™ Documentation Navigator Installation (Windows)Affected
  • =No fix planned
Fixed in–

AI-suggested

Employ application whitelisting and restrict write permissions on directories searched for DLLs by the application. Use Windows security features such as Controlled Folder Access and AppLocker to prevent unauthorized DLL loading. Educate users to avoid executing untrusted files or interacting with suspicious prompts related to Vivado™. Consider running the software in isolated environments or virtual machines with limited privileges. Monitor systems for unusual DLL loads or privilege escalation attempts using endpoint detection and response (EDR) tools. Regularly audit and harden Windows search paths and environment variables to prevent DLL hijacking. If feasible, evaluate alternative tools or workflows that do not rely on the vulnerable component. Maintain up-to-date backups to recover from potential compromise.

Description

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

References

Community reviews

Loading reviews…