One update covers many file formats
ClamAV published 1.5.5 and 1.4.7 on 18 November 2026. The security changes cover logging, email URL canonicalization, executable unpackers, CHM and OLE2 parsing, InstallShield and XAR extraction. A single engine update can therefore address several different ways that crafted files affect a scanner.
The affected version ranges vary by issue. Do not treat one CVE’s range as the range for the entire release. Use the ClamAV release note for each flaw and check the product supplier’s build if the engine is bundled.
Find all scanning paths
List mail gateways, upload services, endpoint agents, file shares, container images and products that scan files with ClamAV. Record the engine version, package source, owner and update method. Include temporary and disaster-recovery systems.
Check whether scanners receive archives or large files, where temporary extraction data is stored, and how queue delays are reported. These details help identify systems where a parser issue could affect service capacity.
Patch, restart and verify
Update to 1.4.7 or 1.5.5 through the supported channel. Restart long-running processes and rebuild container images so the patched library is loaded. Confirm scanner health, file queue processing, database updates and quarantine actions.
Keep the change record with the version and source. If a supplier has not released a fixed build, ask for a delivery date and the supported interim guidance. CYPEE Cyber can assess an approved server or application scope and help verify remediation.
