Virtuozzo Infrastructure 7.4 Hotfix 2 (7.4.0-80)¶
Issue date: 2026-08-20
Applies to: Virtuozzo Infrastructure 7.4
Virtuozzo Advisory ID: VZA-2026-023
1. Overview¶
This update provides stability and security fixes.
2. Bug Fixes¶
A security fix for CVE-2026-64531. (VSTOR-140619)
A security fix for CVE-2026-64561. (VSTOR-140678)
Storage version bumping could remain disabled until the end of a cluster update, delaying operations such as an SPLA license upgrade. (VSTOR-87519)
The compute service container could remain stopped on a node after a failed cluster update. (VSTOR-125431)
Maintenance could be stopped while a cluster update was running, allowing nodes to be rebooted unexpectedly. (VSTOR-126182)
The admin panel could fail to load with HTTP 500 on secondary high availability nodes after an update. (VSTOR-128648)
A node already in maintenance before a cluster update could have its compute service re-enabled after the update, allowing VMs to migrate to it. (VSTOR-131556)
Deleting an S3 bucket with a very large number of objects could be extremely slow; a delete-by-prefix operation is now available. (VSTOR-140023)
NFSv4 directory metadata operations could intermittently return a remote I/O error immediately after directory creation, disrupting Kubernetes workloads on NFS shares. (VSTOR-140223)
Workload reports now include the product name and version of applications discovered on Windows VMs. (VSTOR-140228)
The backup storage could repeatedly replay the same journal without advancing, stalling backup traffic. (VSTOR-140445)
Workload reports could retain data from the previous host after a VM was live migrated. (VSTOR-140477)
An empty conflict list could be shown in the UI when the update path included a version that could not be skipped. (VSTOR-140904)
Supported Kubernetes version limits were not defined for versions 7.3 and later, preventing update eligibility from being validated. (VSTOR-140988)
The message for a mandatory upgrade step did not specify which version to upgrade to first. (VSTOR-141189)