Release Information for Veeam ONE 12 and Updates

What's New

Veeam ONE 12.3 Patch 1 is a cumulative maintenance and security update for Veeam ONE 12.3. It resolves reported issues across reporting, monitoring, alarms, licensing, and integrations, adds REST API and ServiceNow enhancements, and addresses externally reported security vulnerabilities. Applying this patch is recommended for all Veeam ONE 12.3 deployments.

New Features and Improvements

Cloud Backup Sizes in the REST API
The public REST API now reports the size of cloud backups and of their restore points.

AWS Account Identification
Veeam ONE now collects the AWS Account ID and account alias for workloads protected by Veeam Backup for AWS, and the public REST API returns both for protected Amazon EC2 workloads.

Customizable ServiceNow Short Description
The short description of incidents created in ServiceNow can now be customized.

Resolved Issues

Security

• CVE-2026-58074 | Severity: High (8.6)
  A vulnerability allowing a high-privileged user to execute arbitrary code on the server.
• CVE-2026-64631 | Severity: High (8.6)
  A vulnerability allowing a low-privileged user to inject SQL and extract database contents.
• CVE-2026-64632 | Severity: High (8.5)
  A vulnerability allowing a low-privileged user to capture the NTLM credentials of the Reporter service account.

Alarms

• Veeam ONE repeatedly logs an error because triggered alarms are not synchronized correctly between the alarm cache and the database:

  Cannot insert the value NULL into column 'triggered_alarm_id'
  

• The Backup Copy RPO alarm reports incorrect information because deleted backup copy workers are still taken into account.
• The Backup Job State alarm does not raise a Warning when a backup job session finishes with a warning.
• The Suspicious Incremental Backup Size alarm produces false-positive triggers for Proxmox VE backup jobs.
• The License exceeded for Veeam Backup for Microsoft 365 alarm uses an incorrect threshold. The threshold can now be configured with the VbmLicenseCapacityDepletingThreshold registry value.
• Backup policy sessions for Microsoft Azure workloads trigger false-positive alarms.
• The Unusual Job Duration rule cannot be added to a newly created empty alarm.

Reporting

• The Workload Protection History report shows restore points of SAP HANA plug-in backup jobs beyond the retention configured in Veeam Backup & Replication.
• The Job Configuration Change Tracking report fails when a job name contains leading or trailing spaces, with the error:

  Failed to get data set 'User' from report template
  

• The Job Configuration Change Tracking report does not show the names of objects added to or removed from a job.
• The Host Configuration Chargeback report includes virtual machines that have already been deleted from the infrastructure.
• The Custom Infrastructure report cannot be generated for Veeam Agent objects because of duplicate records in the report data set.
• The Data Sovereignty Overview report does not show backups stored in public cloud object storage repositories.
• The GFS Backup Files report fails to generate with the error:

  Failed to retrieve report data. Unable to load dataset 'dsData' from the database
  

• The Backups on Tape report cannot be generated in large environments and fails after a long timeout with the error:

  Unable to load dataset from the database
  

• The Backup Billing report counts backed-up virtual machines per job instead of per job-and-repository combination.
• The Tape GFS Backup Files report fails when the report data exceeds the database column length limit, with the error:

  Unable to load dataset 'dsSummary'
  

• The Capacity Planning for Backup Repositories report calculates incorrect values for S3-compatible object storage repositories.
• The Protected Computers report includes failover clusters that should not appear in the report.
• The Backups on Tape report displays restore points that have already been deleted.
• The Restore Sessions by Application Type chart in the Restore Operator Activity report for Veeam Backup for Microsoft 365 shows incorrect data when a one-day reporting period is selected.
• Editing the description of a saved report also resets the report scope.
• The Protected Cloud Instances report does not show the protection status of some Microsoft Azure objects.
• The Custom Infrastructure report truncates guest OS names that exceed the database column length limit. The column length has been increased.
• The Immutable Workloads report shows duplicate entries, and shows only the original backup job name for virtual machines protected by backup, backup copy, and backup-to-tape jobs.
• The Latest Job Status report calculates the number of job retries incorrectly.
• The Backups on Repository report shows invalid last backup dates after an upgrade of Veeam Backup & Replication.
• The GFS Backup Files report is missing restore points created by backup copy jobs.
• The Infrastructure Overview (Visio) report cannot be generated and fails with the error:

  Can not get VLANID property for object: NSX (Network)
  

• The SLA Compliance report for Veeam Backup for Microsoft 365 calculates the number of restore points incorrectly.
• The SureBackup Job Status chart in the Recovery Verification Overview report calculates job statuses incorrectly.

Monitoring and Data Collection

• Object properties data collection from VMware vCenter Server completes with warnings when the vCenter Server uses an untrusted SSL certificate.
• Storage consumption information for Veeam Cloud Connect tenants is not updated because deleted entities are included in the data collection scope.
• Data collection from a Veeam Backup & Replication server stops because of a numeric overflow in the Veeam ONE database.
• Virtual switches are not collected from stand-alone Microsoft Hyper-V clusters.
• CPU usage charts may display values that exceed 100%.
• Veeam ONE Client does not show Capacity Planning details for Veeam Backup for Microsoft 365 backup repositories.
• Free and used space is not displayed for Veeam Backup for Microsoft 365 repositories backed by Azure Blob storage.
• The 24110 Cloud Connect tenant has been created event is not displayed in the Veeam ONE event viewer.

Scalability and Performance

• The Veeam ONE database may become blocked by long-running transactions, which interrupts data collection and reporting.
• Veeam ONE performance degrades significantly in large environments.
• Memory consumption of the Veeam ONE data collection service grows over time in large environments.
• Scheduled generation of the Latest Job Status report fails in large environments because of excessive memory consumption.

Licensing

• License usage may be overstated because of duplicate virtual machine records, and the Applications workload type does not show details about consumed instances.
• The number of used license instances does not match the number of managed objects.
• Virtual machines that consume a license are not shown in the list of licensed virtual machines.
• Veeam ONE reports incorrect current license usage, which affects license reporting in Veeam Service Provider Console.

Integrations

• Alarm descriptions sent to ServiceNow are truncated, so incidents do not contain the full alarm details.
• Incidents created in ServiceNow are not resolved when the corresponding Veeam ONE alarm returns to the Resolved state.
• The cmdb_id value cannot be used as a variable when configuring Veeam ONE integration with ServiceNow incidents.
• Alarm notifications are no longer delivered to the syslog server after a period of inactivity.

Business View

• Business View operations take a significant amount of time to complete in large environments.
• A virtual machine that was excluded from a manually created Business View group cannot be added back on the Virtual Machines tab.

Jobs Calendar

• Jobs Calendar does not display charts and fails with the error:

  When converting a varchar data type to a datetime data type, the value is outside the valid range
  

• Jobs Calendar shows incorrect future run dates and times for a job until the job runs at least once.

Veeam ONE Web Client

• The Backup Immutability Status widget fails to load and returns an error.
• The Backup Infrastructure Inventory widget shows unexpected data, and backup policy status is displayed incorrectly in Veeam ONE Client.
• The Protected VMs Overview widget displays an incorrect full backup size.
• The Repository Free Space heatmap widget displays only a limited number of repositories.
• Veeam Threat Center cannot be opened because of an incorrect dashboard position calculation, and returns the error:

  Cannot find the Veeam Threat Center dashboard
  

REST API

• The /protectedData/virtualMachines REST API method returns incorrect values, and restore point data is calculated incorrectly for scale-out backup repositories. Two additional fields have been added to the method output.

Installation and Upgrade

• Installing a Veeam ONE patch (.msp) from the command line in unattended mode fails with the error:

  User name could not be empty
  

• Alarms exported from Veeam ONE 12.2 cannot be imported into Veeam ONE 12.3.

General

• Veeam ONE services fail to start when the certificate private key is imported into the user profile instead of the local machine certificate store.
• The Veeam ONE service fails to start with an entity cache error:

  Entity not found