# CVE-2025-48506: Other in Vitis™ Unified Installer for FPGAs & Adaptive SoCs in Windows

> Local attackers can inject DLLs into Vitis Unified installation paths on Windows, leading to arbitrary code execution.

- **Severity:** High 7.3 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-5qgc-w3gc-w4mc

## What is CVE-2025-48506?

CVE-2025-48506 is a high-severity vulnerability in AMD Vitis™ Unified Installer for FPGAs & Adaptive SoCs in Windows, published on 11 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Uncontrolled search paths in Vitis™ Unified installation path on local Windows machines could allow DLL injection into these install paths, potentially resulting in arbitrary code execution.

Weakness: CWE-427 (Uncontrolled Search Path Element)

## Which versions are affected by CVE-2025-48506?


## How do I fix CVE-2025-48506?

No fix has been published for CVE-2025-48506 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-48506 being exploited?

There is no known exploitation of CVE-2025-48506 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-48506 and fix it if it is affected.

What it is: CVE-2025-48506 is a high-severity vulnerability in AMD Vitis™ Unified Installer for FPGAs & Adaptive SoCs in Windows, published on 11 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-48506 in the wild and no public exploit code.

Affected product: AMD Vitis™ Unified Installer for FPGAs & Adaptive SoCs in Windows. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-48506/ (Markdown: https://insights.sbomify.com/CVE-2025-48506/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-48506
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-48506
- OSV: https://osv.dev/vulnerability/CVE-2025-48506

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-48506/
Summaries are generated and may contain mistakes; the official description above is the record.