End of life (EOL) policy change
0.103 support extension
- Expected End of Life (EOL): Sept. 14, 2024
- Patch versions continue until: Sept. 14, 2024
- Internal signature load testing until: Sept. 14, 2024
- Database downloads allowed until: Sept. 14, 2025
Effective March 28, 2023, ClamAV 0.104.0 (and all patch versions) will no longer be supported in accordance with ClamAV's EOL policy.
End of life (EOL) for ClamAV means:
Please upgrade to a supported version of ClamAV, currently at 0.103.8, 0.105.2, and 1.0.1, available for download now.
ClamAV versions 0.103.5 and 0.104.2 are now available for download on the clamav.net Downloads page.
We would also like to take this opportunity to remind users that versions 0.102 and 0.101 have reached their end-of-life period. These versions exceeded our EOL dates on Jan. 3, 2022 and will soon be actively blocked from downloading signature database updates.
For additional details about ClamAV's end-of-life policy, please see our online documentation.
As a reminder, the ClamAV 0.100 release will reach its end of life (EOL) in one month's time on Oct. 29, 2021. After this date, ClamAV 0.100 and all patch versions will be blocked from downloading new signatures from database.clamav.net.
For information about the EOL policy, visit the ClamAV online documentation.
Effective Oct. 29, 2021, ClamAV 0.100.0 (and all patch versions) will no longer be supported in accordance with ClamAV's EOL policy.
End of life (EOL) for ClamAV means:
Please upgrade to the newest version of ClamAV, currently at 0.103.3, available for download now!
As always, thank you for using ClamAV.
ClamAV community, we want to inform you that, effective March 1, ClamAV 0.99.0 (and all minor versions) will no longer be supported in accordance with ClamAV's EOL policy. For clarification, anything prior to 0.100.0.
End of life (EOL) for ClamAV essentially means that we will no longer be testing against that version when we write signatures, and we may break something with a future release. So, while signatures may work past March 1, we are no longer testing that configuration.