# CVE-2023-27532: Veeam Backup & Replication Cloud Connect Missing Authentication for Critical Function

> Attackers can obtain encrypted credentials from the configuration database, potentially gaining access to backup infrastructure hosts.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Yes, since 22 Aug 2023 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Mar 2023
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-hh3c-xpmg-w5fr

## What is CVE-2023-27532?

CVE-2023-27532 is a high-severity vulnerability in Veeam Backup & Replication, published on 10 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in Veeam Backup & Replication component allows encrypted credentials stored in the configuration database to be obtained. This may lead to gaining access to the backup infrastructure hosts.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2023-27532?

It affects 1 product.


Products: Veeam Veeam Backup \& Replication.

## How do I fix CVE-2023-27532?

No fix has been published for CVE-2023-27532 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 12 Sep 2023.

## Is CVE-2023-27532 being exploited?

Yes. Attackers have exploited CVE-2023-27532 in the wild since at least 22 Aug 2023, including in ransomware campaigns.

Public exploit code:

- Exploit for CVE-2023-27532 against Veeam Backup & Replication (github_poc): https://github.com/sfewer-r7/CVE-2023-27532
- POC for Veeam Backup and Replication CVE-2023-27532 (github_poc): https://github.com/horizon3ai/CVE-2023-27532
- https://github.com/puckiestyle/CVE-2023-27532-RCE-Only (github_poc): https://github.com/puckiestyle/CVE-2023-27532-RCE-Only
- https://github.com/yunus-a1i/veeam-cve-2023-27532-mock (github_poc): https://github.com/yunus-a1i/veeam-cve-2023-27532-mock

## Other vulnerabilities in Veeam Backup & Replication

- [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-2022-26500](https://insights.sbomify.com/CVE-2022-26500/): Veeam Backup & Replication Remote Code Execution (high 8.8, 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-2023-27532 and fix it if it is affected.

What it is: CVE-2023-27532 is a high-severity vulnerability in Veeam Backup & Replication, published on 10 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2023-27532 in the wild since at least 22 Aug 2023, including in ransomware campaigns.

Affected product: Veeam Backup & 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-2023-27532/ (Markdown: https://insights.sbomify.com/CVE-2023-27532/index.md)
```

## Sources

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

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