CVE-2026-106076 A vulnerability allowing an authenticated organization-transfer peer to inject SQL into the configuration database of the source Veeam Backu
Critical 9.0
Published
Updated
Check this codebase for CVE-2026-106076 and fix it if it is affected.
What it is: CVE-2026-106076 is a critical vulnerability in Veeam Backup for Microsoft 365, published on 27 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-106076 in the wild and no public exploit code.
Affected product: Veeam Backup for Microsoft 365. 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-106076/ (Markdown: https://insights.sbomify.com/CVE-2026-106076/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-106076?
CVE-2026-106076 is a critical vulnerability in Veeam Backup for Microsoft 365, published on 27 Oct 2026.
Official description
A vulnerability allowing an authenticated organization-transfer peer to inject SQL into the configuration database of the source Veeam Backup for Microsoft 365 server, leading to cross-tenant read and write of configuration data and remote code execution as the PostgreSQL service account.
Weakness: CWE-89
Which versions are affected by CVE-2026-106076?
How do I fix CVE-2026-106076?
No fix has been published for CVE-2026-106076 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-106076 being exploited?
There is no known exploitation of CVE-2026-106076 in the wild and no public exploit code.
Sources
Also known as GHSA-cvj7-8m64-3q4v.