# CVE-2026-44963: Deserialization in Backup and Replication

> An authenticated domain user can achieve remote code execution on the Veeam Backup Server via a deserialization vulnerability.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jun 2026
- **Updated:** 10 Jun 2026
- **Also known as:** GHSA-qgvw-vfmj-prrg

## What is CVE-2026-44963?

CVE-2026-44963 is a critical unsafe deserialization vulnerability in Veeam Backup and Replication, published on 9 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability allowing remote code execution (RCE) on the Backup Server by an authenticated domain user.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2026-44963 being exploited?

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

Public exploit code:

- Detection scripts, patch checker & hardening guide for CVE-2026-44963 (Veeam B&R RCE) (github_poc): https://github.com/jockerjml/CVE-2026-44963-veeam-checker
- CVE-2026-44963 - Draft - Veeam (github_poc): https://github.com/HORKimhab/CVE-2026-44963

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44963 is a critical unsafe deserialization vulnerability in Veeam Backup and Replication, published on 9 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-44963 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-44963/ (Markdown: https://insights.sbomify.com/CVE-2026-44963/index.md)
```

## Sources

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

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