# CVE-2024-40711: Veeam Backup and Replication Deserialization

> Unauthenticated attackers can achieve remote code execution via deserialization of untrusted data in Veeam Backup and Recovery.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 17 Oct 2024 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Sep 2024
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-c76v-gjqc-j462

## What is CVE-2024-40711?

CVE-2024-40711 is a critical unsafe deserialization vulnerability in Veeam Backup and  Recovery, published on 7 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A deserialization of untrusted data vulnerability with a malicious payload can allow an unauthenticated remote code execution (RCE).

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2024-40711?

It affects 1 product.


Products: Veeam Veeam Backup \& Replication.

## How do I fix CVE-2024-40711?

No fix has been published for CVE-2024-40711 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 7 Nov 2024.

## Is CVE-2024-40711 being exploited?

Yes. Attackers have exploited CVE-2024-40711 in the wild since at least 17 Oct 2024, including in ransomware campaigns.

Public exploit code:

- Pre-Auth Exploit for CVE-2024-40711 (github_poc): https://github.com/watchtowrlabs/CVE-2024-40711
- CVE-2024-40711-exp (github_poc): https://github.com/realstatus/CVE-2024-40711-Exp
- Veeam Backup & Replication - Unauthenticated (nuclei): http/cves/2024/CVE-2024-40711.yaml

## Other vulnerabilities in Veeam Backup and  Recovery

- [CVE-2022-26501](https://insights.sbomify.com/CVE-2022-26501/): Veeam Backup & Replication Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2022-26500](https://insights.sbomify.com/CVE-2022-26500/): Veeam Backup & Replication Remote Code Execution (high 8.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-2024-40711 and fix it if it is affected.

What it is: CVE-2024-40711 is a critical unsafe deserialization vulnerability in Veeam Backup and  Recovery, published on 7 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2024-40711 in the wild since at least 17 Oct 2024, including in ransomware campaigns.

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

## Sources

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

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