EOL.Wiki EOL.Wiki
← ← Back to all products

ClamAV

Active
Security & Networking Latest Version: 1.5.1 Latest Release: Oct 16, 2025

ClamAV is an open-source antivirus engine for detecting trojans, viruses, malware, and other threats.

Versions

13

Latest Version

1.5.1

Active Support

2

EOL

11

Lifecycle Timeline

Today
1.5
1.5
1.4
1.4
1.3
1.3
1.2
1.2
1.1
1.1
1.0
1.0
0.105
0.105
0.104
0.104
0.103
0.103
0.102
0.102
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
1.5Oct 7, 2025-No1.5.1No
Active
1.4Aug 15, 2024-Aug 15, 20271.4.3
Yes
Active
1.3Feb 7, 2024-Feb 7, 20261.3.2No
EOL
1.2Aug 27, 2023-Dec 15, 20241.2.3No
EOL
1.1May 1, 2023-Jun 7, 20241.1.3No
EOL
1.0Nov 28, 2022-Nov 28, 20251.0.9
Yes
EOL
0.105May 4, 2022-Sep 1, 20230.105.2No
EOL
0.104Sep 2, 2021-Mar 28, 20230.104.4No
EOL
0.103Sep 11, 2020-Sep 14, 20240.103.12
Yes
EOL
0.102Oct 2, 2019-Jan 3, 20220.102.4No
EOL
0.101Dec 2, 2018-Jan 3, 20220.101.5No
EOL
0.100Apr 4, 2018-Oct 29, 20210.100.3No
EOL
0.99Nov 25, 2015-Mar 1, 20210.99.4No
EOL

Frequently Asked Questions

Which versions of ClamAV have reached end of life?
The following ClamAV versions have reached end of life and no longer receive security updates: 1.3, 1.2, 1.1, 1.0, 0.105, 0.104, 0.103, 0.102 (and 3 more). It is recommended to upgrade to a supported version.
Is it safe to continue using ClamAV 1.3?
ClamAV 1.3 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of ClamAV?
The latest version of ClamAV is 1.5.1, released in the 1.5 release cycle.
How many versions of ClamAV are currently supported?
ClamAV currently has 2 actively supported version(s): 1.5, 1.4.
When does ClamAV 1.5 reach end of life?
ClamAV 1.5 does not have a specific end-of-life date announced yet.
What should I do when ClamAV reaches end of life?
When a ClamAV version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.