SOCLYDE logo
Current languageEN
VulnerabilityVeeamBackup securityCredentials

Veeam fixes credential exposure flaw in Backup Viewer

CVE-2026-93026 could let a Backup Viewer change Veeam Enterprise Manager's master key and stored antivirus-update credentials; Veeam has released a fix.

Published on

By Soclyde Team

Archival backup media and a labelled-free storage case on a quiet workbench

In summary

  • CVE-2026-93026 affects Veeam Backup Enterprise Manager and requires an account with the Backup Viewer role.
  • The flaw could allow changes to the master key and stored antivirus-update credentials; it is not described as remote code execution.
  • Veeam fixed the issue in version 12.3.2.4934; review role assignments and rotate credentials if exposure is suspected.

Explore next

Soclyde resources

Article contents

Veeam has published a fix for CVE-2026-93026 in Backup Enterprise Manager. The issue requires an account with the Backup Viewer role and could expose sensitive configuration material. Veeam's advisory describes changes to a master key and stored antivirus-update credentials, not remote code execution.

What the vulnerability allows

An attacker with the required Backup Viewer access could modify the Enterprise Manager master key and credentials used for antivirus updates. The practical risk depends on who can reach the management interface and how the role is assigned. The reported CVSS v4 score is 6.1, a medium severity rating; it does not measure the value of credentials in a particular environment.

Identify affected installations

Check whether Backup Enterprise Manager is deployed and compare its version with Veeam's KB4934 advisory. Veeam lists version 12.3.2.4934 as containing the fix. Follow the vendor's version-specific instructions, including any prerequisites, rather than assuming all Backup & Replication deployments have identical exposure.

Update role assignments

Upgrade affected deployments and confirm the running version. Review which users and service accounts have Backup Viewer access, remove assignments that are no longer needed, and protect the remaining accounts with strong authentication. Restrict access to the management interface to trusted administrative networks where practical.

Assess credential exposure

If the vulnerable version was accessible to an account or person that should not have had this role, investigate changes to the master key and antivirus-update settings. Rotate affected credentials where exposure is plausible, and record the changes in your incident process. The public advisory does not establish that attackers exploited the flaw in the wild.

Keep recovery systems protected

Backup management systems can contain credentials and configuration needed during recovery. Store their administrator credentials securely and separately from the systems they protect, and limit who can retrieve or change them. Soclyde helps teams organise account credentials; it does not patch Veeam or secure a misconfigured backup server. See the secure password generator guide for account hygiene.

Upgrade to Veeam's fixed version, check the Backup Viewer role assignments, and investigate sensitive configuration changes if the system was exposed. Treat credential rotation as a response to plausible access, not as evidence that exploitation happened.

Frequently asked questions

Can an unauthenticated attacker exploit CVE-2026-93026?

The published description requires an account with the Backup Viewer role. Protect those accounts and review who has been assigned that role.

What data or settings are at risk?

Veeam says the flaw could let a Backup Viewer modify the Enterprise Manager master key and stored antivirus update credentials. The advisory does not describe this CVE as remote code execution.

Which version fixes the issue?

Veeam lists version 12.3.2.4934 as the fix. Check the official KB for the affected product versions and upgrade instructions that match your deployment.

References

Sources and references

Need advice?

Design your password strategy with Soclyde

Schedule a dedicated walkthrough with the team to see how local-first security adapts to your stack.

Talk with us

Keep reading