Skip to main content
Mallory
CriticalVulnerability

CVE-2026-106076: SQL Injection and Remote Code Execution in Veeam Backup for Microsoft 365

Published Oct 27, 2026 · Updated 13 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days11 mentions · peak 5 in a dayToday
CVSS9.0Critical · v4
EPSS0.37%31st percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-106076CWE-89 · Improper Neutralization of Special…

CVE-2026-106076 is a SQL injection vulnerability in Veeam Backup for Microsoft 365 that allows an attacker controlling an authenticated organization-transfer peer to inject SQL statements into the source server's configuration database. Successful exploitation enables cross-tenant reading and modification of configuration data and remote code execution as the PostgreSQL service account. Affected versions include 8.x releases through 8.5.0.1014; unsupported releases should also be considered vulnerable. The vulnerability is rated Critical with a CVSS v4.0 score of 9.0 and is fixed in build 8.6.0.1102.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Exploitation compromises the confidentiality and integrity of configuration data across tenant boundaries and permits remote code execution with the privileges of the PostgreSQL service account on the source server. This can compromise the configuration database and affect the confidentiality, integrity, and availability of the server and systems accessible under that account's permissions.

Mitigation

If you can’t patch tonight, do this now.

No vendor-approved temporary workaround is specified. As interim risk reduction, restrict organization-transfer access to trusted, necessary peers and limit network access to the relevant services. These measures do not replace installation of the vendor fix.

Remediation

Patch, then assume compromise.

Upgrade to Veeam Backup for Microsoft 365 8.6, build 8.6.0.1102, or a later fixed release. Prefer 8.6 Patch 1, build 8.6.0.5011, or a later supported release to address this vulnerability and the additional vulnerabilities covered by the same advisory. Upgrade unsupported releases to a supported, patched version.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-106076 exploited in the wild?
As of Nov 4, 2026, Mallory has no reports of CVE-2026-106076 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-106076?
As of Nov 4, 2026, Mallory has found no public exploit for CVE-2026-106076.
Is there a patch for CVE-2026-106076?
Upgrade to Veeam Backup for Microsoft 365 8.6, build 8.6.0.1102, or a later fixed release. Prefer 8.6 Patch 1, build 8.6.0.5011, or a later supported release to address this vulnerability and the additional vulnerabilities covered by the same advisory.
How severe is CVE-2026-106076?
CVE-2026-106076 has a CVSS v4 score of 9.0 (Critical) and an EPSS score of 0.37% (31st percentile) as of Nov 4, 2026.
Activity feed

Recent activity

11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity6Community discussion across Reddit, Mastodon, and other social sources.