# CVE-2026-58070: Information disclosure in Backup and Replication

> Attackers with log read access can recover privileged credentials from cleartext logs in Veeam Backup and Replication.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** GHSA-64r9-cr9x-2wp4

## What is CVE-2026-58070?

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

### Official description

A vulnerability that records guest OS processing credentials in cleartext in a support log on the guest, allowing a user with read access to that log to recover privileged account credentials.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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


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

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

## Is CVE-2026-58070 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-58070 is a medium-severity vulnerability in Veeam Backup and Replication, published on 26 Aug 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-58070 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-58070/ (Markdown: https://insights.sbomify.com/CVE-2026-58070/index.md)
```

## Sources

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

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