# CVE-2022-26500: Veeam Backup & Replication Remote Code Execution

> Remote authenticated attackers can exploit path traversal to access internal APIs and execute arbitrary code on Veeam Backup & Replication servers.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 13 Dec 2022 (CISA KEV), used in ransomware
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Mar 2022
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-2vw2-587w-g9v6

## What is CVE-2022-26500?

CVE-2022-26500 is a high-severity path traversal vulnerability in n/a, published on 17 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper limitation of path names in Veeam Backup & Replication 9.5U3, 9.5U4,10.x, and 11.x allows remote authenticated users access to internal API functions that allows attackers to upload and execute arbitrary code.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2022-26500?

It affects 1 product.


Products: Veeam Veeam Backup \& Replication.

## How do I fix CVE-2022-26500?

No fix has been published for CVE-2022-26500 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 Jan 2023.

## Is CVE-2022-26500 being exploited?

Yes. Attackers have exploited CVE-2022-26500 in the wild since at least 13 Dec 2022, including in ransomware campaigns.

## Other vulnerabilities in n/a

- [CVE-2024-40711](https://insights.sbomify.com/CVE-2024-40711/): Veeam Backup and Replication Deserialization (critical 9.8, exploited in the wild)
- [CVE-2022-26501](https://insights.sbomify.com/CVE-2022-26501/): Veeam Backup & Replication Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2023-27532](https://insights.sbomify.com/CVE-2023-27532/): Veeam Backup & Replication Cloud Connect Missing Authentication for Critical Function (high 7.5, exploited in the wild)
- [CVE-2026-21666](https://insights.sbomify.com/CVE-2026-21666/): Missing authorization in Backup and Replication (critical 10.0)
- [CVE-2026-21667](https://insights.sbomify.com/CVE-2026-21667/): Missing authorization in Backup and Replication (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-26500 and fix it if it is affected.

What it is: CVE-2022-26500 is a high-severity path traversal vulnerability in n/a, published on 17 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2022-26500 in the wild since at least 13 Dec 2022, including in ransomware campaigns.

Affected product: n/a. 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-2022-26500/ (Markdown: https://insights.sbomify.com/CVE-2022-26500/index.md)
```

## Sources

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

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