Recently we discuss the steps to Update Veeam Backup & Replication to Build 13.0.1.2067. Shortly, Veeam released some patches to fix Vulnerable Veeam Backup & Replication 13.0.1.2067 and Earlier. Therefore, in this guide, we shall update our Veeam Backup and Replciation Server to version 13.0.2.29. Please see How to upgrade Veeam One from v12 to v13, and how to Integrate Trellix ePolicy Orchestrator with a Syslog Server.
Note: If you use Enterprise Manager for centralized management, it must always be upgraded first. It cannot manage VBR servers running a newer version than itself.
To learn more about these security issues, refer to the following Veeam Knowledge Base (KB) articles: “4852 (affects v13.0.1.2067), while, 4831 (affects 13.0.1.1071 and earlier), and 4858 (affects Veeam ONE).
Veeam Security Updates and Build References Overview
The table below provides an overview of the latest Veeam security updates, cumulative patches, and build references affecting Veeam Backup & Replication and Veeam ONE deployments. These updates address multiple security vulnerabilities, platform stability issues, and operational improvements that you should review and apply to safeguard your systems.
| KB | Update Type | Affected Product | Purpose / Fix | Severity | Requires Reboot | Recommended Action | Notes |
|---|---|---|---|---|---|---|---|
| KB4831 | Security Update | Veeam Backup & Replication | Addresses multiple security vulnerabilities and stability fixes | Critical | Yes | Install immediately on all affected VBR servers | Ensure all remote components and proxies are upgraded afterward |
| KB4852 | Cumulative Patch | Veeam Backup & Replication | Resolves post-upgrade issues and improves platform stability | High | Recommended | Apply during maintenance window | Updates VBR to build 13.0.2.29 |
| KB4858 | Security Fixes & Improvements | Veeam ONE | Resolves vulnerabilities and introduces security-related improvements | High | Recommended | Upgrade Veeam ONE servers to the latest build | Review monitoring services and reporting functionality after upgrade |
| KB3103 | Product Build Reference | Veeam Backup & Replication | Official build numbers and version mapping reference | Informational | No | Use to verify installed build versions | Useful for compliance validation and troubleshooting |
Please see Veeam Backup and Replication: PowerShell must be Remote Signed, how to Prevent Automatic Driver Updates in Windows and Xen-Orchestra, and Switch from IP Addresses to DNS for Backup Infrastructure in VBR.
Download VBR 13.0.2.29 ISO
Because Veeam updates are delivered through cumulative installer-based upgrades. You are required to download and mount the latest Veeam installation ISO before applying the fixes.
Note: It is also important to verify that all associated infrastructure components such as backup proxies, repositories, WAN accelerators, and monitoring servers are updated to supported builds after patching the primary Veeam Backup & Replication server.
You can use the following hyperlink to downloaded the latest ISO.
You will be required to login in order to be able to download the image. If you do not already have an account, please do so.
Before proceeding to apply the patch, we are currently running Veeam Backup and Replication 13.0.1.2067, and we affected by “KB 4852“. Therefore, with the latest ISO download contains all the cumulative updates and security fixes.
Please see Fix broken Repository Path in Veeam Scale-Out Backup Repository, how to remove a Repository from Veeam Backup and Replication, and how leverage Azure Blob Storage as an Object Storage Repo in Veeam.
Mount ISO
After downloading the ISO, open the file properties
Next, click “Unblock” option is selected before mounting or extracting the file. Since the ISO was downloaded from the internet, Windows marks it with a security identifier (Mark of the Web), which can prevent certain files or scripts from executing correctly.
Unblocking the file removes this restriction and helps avoid installation or execution issues during the upgrade process.
Next mount the file by right-clikinmg on the downloaded ISO and clicking on “Mount”.
After you mount the image or insert the disk, Autorun opens a splash screen. If Autorun is not available or disabled, run the Setup.exe file from the image or disk as shown below.
Please see Configure Windows Device Inactivity Limit Locally and Domain Wide, How to create a Dev Drive on Windows 11, and how to Kill Containers and remove unused images from Docker Correctly.
Upgrade VBR v13.0.2.29
Click on upgrade to proceed to v13.0.2.29
I will not discuss the entire steps as we have dealth with this topic severally in the past. For similar articles, please see “How to upgrade Path and In-Place Upgrade for VBR v13 and Known Fixes, how to upgrade Veeam Backup and Replication 12.3, and how to upgrade Veeam Backup and Replication v12.3 to v13 on Windows“.
Next, click on upgrade on Veeam Backup & Replication to proceed.
Follow the prompts in the wizard and accept the license agreement. During the license step, your existing license should be automatically detected. Click Next to continue, or choose Login or Browse to locate and import your existing license file manually.
Shortly, the license will be validated and the system configuration check will kick in as well. This will check and apply missing components.
As you can see below, a server restart is required in order to proceed with thee installation.
On the prompt to reboot, click on Yes.
Please see how to Install and update PowerShell version 7 on Windows and Linux or follow the steps below. You may also find the following interesting “Upgrade PowerShell Core Windows or Mac and Linux System“. Here is how to update PowerShell and Package Management via GPO.
Upon restart, run the setup file again and at the upgrade step. If there are errors during the configuration check, they will be prompted.
To fix this, see “how to Add Another Hard Drive to a Virtual Machine in HyperV“, how to extend a VM Hard Disk on VMware Workstation, and how to Shrink and Compact Virtual Hard Disks in Hyper-V.
Also do not fail to delete any any outdated job that is not relevant and needed.
At this time, I have added a new partition. I will merge this in the future and now now.
As you can see below, this is a warning only and we can proceed to have VBR upgraded to the latest version. To merge the above partitions, we will be needed Aomei free partition manager. Please see “Fix unable to Extend Volume on Windows protected by BitLocker” due to non-adjency the partitions.
Select the Update remote components automatically check box. Otherwise, the backup server will prompt you to upgrade them during the first run of the backup server after the update.
Please see “Hyper V Disk allocation: Why Veeam reports full size after Shrinking, and how to Increase Disk Size in Hyper-V.
VBR Upgrade Status
This is the core engine. As you can see, the upgrade has stated and the VBR server is currently being upgraded.
Upgrading VBR Console. You must upgrade any standalone consoles installed on workstations or separate servers must be updated next to match the exact version of the newly upgraded VBR server. Please see how to install Veeam Backup Console on a Jump Server, and
Veeam Explorers are being upgraded
Veeam Agents Redistributables are being upgraded
Plug-ins are being upgraded
Installation is being finalized and services are being started.
Note: If any services fails, retry any failed servce. Else, you may have to recover oyur VBR environemnt as dioscussedhere “[World Backup Day] V13 Upgrade Failure: Veeam Configuration Backup Saved the Day“.
Click on Finish to complete the update process.
As you can see the upgrade to version 13.0.2 has succeeded.
Please see Monitoring Synology with Prometheus and Grafana, how to Harden your Veeam Backup Server with Microsoft AppLocker, and Force BitLocker Recovery: Perform BitLocker Recovery via the Self-Service Portal and Helpdesk.
Launch VBR Console
Upon launching the Veeam Backup and Replication Console, if there are updates, you will be required to patch it.
As you can see we have successfully upgradeed VBR to Build 13.0.2.29
I hope you found the followng on how to fix Vulnerable Veeam Backup and Replication 13.0.1.2067 and Earlier very useful. Please feel free to leave a comment below.
