ClamAV version 0.103 will reach its end of life (EOL) for database updates on September 14, 2025. After this date, this version will no longer receive the latest virus definitions.
To ensure your systems remain protected, please upgrade to the latest supported version of ClamAV before the end-of-life date. This will provide continued access to essential security updates and features.
We recommend that users update to the newest release, ClamAV 1.4 LTS. For users that are unable to upgrade to version 1.4, you may find that ClamAV 1.0 LTS is more suitable. The most recent version of ClamAV can be found on the ClamAV Downloads page, on the ClamAV GitHub Releases page, and through Docker Hub. Information about how to install ClamAV is available in our online documentation.
The following is a list of major changes available to users in the newest versions of ClamAV.
ClamAV 1.0 LTS improves upon ClamAV 0.103 with features such as:
- A new detection capability based on comparing image fuzzy hashes
- [Windows] A feature to start ClamD and Freshclam as Windows services
- [Windows] A feature to scan process memory with either ClamScan or ClamDScan
- Signature database load progress bars for ClamScan
- Support for extracting images from OLE2-based Excel documents
- The ability to use *.cat files with CRB signature rules to trust signed Windows executables
- Support for decrypting read-only OLE2-based XLS files that are encrypted with the default password
- Significant reliability improvements to the All-Match scanning mode Multiple libclamav API improvements
ClamAV 1.4 LTS improves upon ClamAV 1.0 with features such as:
- Support for extracting Universal Disk Format (UDF) partitions
- Support for extracting ALZ archives
- Support for extracting LHA/LZH archives
- Support for extracting images embedded in HTML CSS style-blocks
- Support for extracting attachments found in Microsoft OneNote files
- An option to customize the size of ClamAV's clean file cache
- Effective removal of the MaxScanSize limit so the total amount of data scanned when scanning a file or archive may exceed 4GB. Note: This does not allow individual file size to exceed the 2GB limit
- The ability for Freshclam to use a client certificate PEM file and a private key PEM file for authentication to a private mirror
- A new ClamScan and ClamD option to fail to load if the provided signature database is older than a given number of days
- Multiple libclamav API improvements
You can learn more about ClamAV's End of Life policy here. If you have any questions, please ask on our mailing list or in the ClamAV Discord.
Thank you for your continued support.
