Zarro Technology · Security briefing

Today’s shorter briefing focuses on Veeam’s newly published product guidance for a previously covered Linux kernel vulnerability. The development is the backup-specific remediation path, including components that can be overlooked when the main backup server runs Windows.

1. Veeam: Linux kernel remediation extends to backup helpers and recovery media (Critical)

CVE-2026-98432

What changed

Veeam’s 6 November impact statement covers Linux-kernel components across backup appliances and helper systems. It describes denial of service or memory corruption; it does not confirm exploitation against Veeam. Critical is the underlying kernel severity, rather than a new product-specific score.

Checks and remediation

For Software Appliance and Infrastructure Appliance 13.1, use Veeam Updater and verify installation history; a restart may be required. The fixed appliance kernel is 5.14.0-570.60.1+27.2.el9_6_ciq. Check repositories, proxies and Cloud Connect roles as well as the backup server.

Windows-based Backup & Replication 13.1.2.57 needs the private fix for Linux helper appliances, or the repacked installation media. Veeam’s release history confirms the 6 November ISO repack includes the correction; an older ISO with the same product build number is insufficient evidence of remediation.

The 12.3 helper-appliance fix remains pending in the impact statement. Follow that page for availability. Redeploy persistent Virtual Labs/Azure helpers as instructed and replace recovery media created before remediation.

Investigation

No campaign-specific IoCs are provided. Investigate unexpected appliance crashes or backup failures without treating them as proof of exploitation. Verify backup and restore operations after maintenance. Updating does not establish that earlier suspicious activity was harmless.

Sources: Veeam KB4966: affected components and remediation · Veeam KB4738: 6 November installation-media repack

Zarro Technology