# CVE-2026-56844: Privilege escalation in Backup and Replication

> A local user can exploit a path traversal flaw in the Veeam Updater to gain root-level access to the underlying operating system.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jul 2026
- **Updated:** 22 Jul 2026
- **Also known as:** GHSA-72f6-c934-4fg9

## What is CVE-2026-56844?

CVE-2026-56844 is a high-severity vulnerability in Veeam Backup and Replication, published on 22 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in the Veeam Updater component of the Veeam Software Appliance that could allow a local user to elevate their privileges and gain root-level access to the underlying operating system.

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

## Which versions are affected by CVE-2026-56844?


## How do I fix CVE-2026-56844?

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

## Is CVE-2026-56844 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-56844 and fix it if it is affected.

What it is: CVE-2026-56844 is a high-severity vulnerability in Veeam Backup and Replication, published on 22 Jul 2026. 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-2026-56844 in the wild and no public exploit code.

Affected product: Veeam Backup and Replication. 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-2026-56844/ (Markdown: https://insights.sbomify.com/CVE-2026-56844/index.md)
```

## Sources

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

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