# CVE-2025-64391: Path traversal in Agent for Windows

> A low-privileged local user can exploit arbitrary file write during installation to achieve privilege escalation or code execution.

- **Severity:** Medium 4.1 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:P/VC:N/VI:H/VA:N/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-5r3x-99rx-26hr

## What is CVE-2025-64391?

CVE-2025-64391 is a medium-severity path traversal vulnerability in Veeam Agent for Windows, published on 7 Oct 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

This vulnerability in Veeam Agent for Microsoft Windows allows a low-privileged local user to make the agent write files to arbitrary locations when an administrator installs it.

Weakness: CWE-1386 (Insecure Operation on Windows Junction / Mount Point)

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


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

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

## Is CVE-2025-64391 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-64391 is a medium-severity path traversal vulnerability in Veeam Agent for Windows, published on 7 Oct 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-64391 in the wild and no public exploit code.

Affected product: Veeam Agent for 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-64391/ (Markdown: https://insights.sbomify.com/CVE-2025-64391/index.md)
```

## Sources

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

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