# CVE-2025-0567: Epic Games Launcher Installer profapi.dll untrusted search path

> Local attackers can exploit an untrusted search path in the Epic Games Launcher installer to execute arbitrary code.

- **Severity:** Low 2.0 (`CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jan 2025
- **Updated:** 21 Jan 2025
- **Also known as:** GHSA-mpw4-p79m-f6xf

## What is CVE-2025-0567?

CVE-2025-0567 is a low-severity path traversal vulnerability in Epic Games Launcher, published on 19 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability classified as problematic was found in Epic Games Launcher up to 17.2.1. This vulnerability affects unknown code in the library profapi.dll of the component Installer. The manipulation leads to untrusted search path. Attacking locally is a requirement. The complexity of an attack is rather high. The exploitation appears to be difficult.

Weakness: CWE-426 (Untrusted Search Path)

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


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

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

## Is CVE-2025-0567 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0567 is a low-severity path traversal vulnerability in Epic Games Launcher, published on 19 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0567 in the wild and no public exploit code.

Affected product: Epic Games Launcher. 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-0567/ (Markdown: https://insights.sbomify.com/CVE-2025-0567/index.md)
```

## Sources

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

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