Complete end-of-life dates, support windows, and security status for all Clamav versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 0.99 | 0.99.4 | Nov 25, 2015 | Mar 1, 2021 | 1895 days past EOL | EOL |
| 0.100 | 0.100.3 | Apr 4, 2018 | Oct 29, 2021 | 1653 days past EOL | EOL |
| 0.101 | 0.101.5 | Dec 2, 2018 | Jan 3, 2022 | 1587 days past EOL | EOL |
| 0.102 | 0.102.4 | Oct 2, 2019 | Jan 3, 2022 | 1587 days past EOL | EOL |
| 0.103 LTS | 0.103.12 | Sep 11, 2020 | Sep 14, 2024 | 602 days past EOL | EOL |
| 0.104 | 0.104.4 | Sep 2, 2021 | Mar 28, 2023 | 1138 days past EOL | EOL |
| 0.105 | 0.105.2 | May 4, 2022 | Sep 1, 2023 | 981 days past EOL | EOL |
| 1.0 LTS | 1.0.9 | Nov 28, 2022 | Nov 28, 2025 | 162 days past EOL | EOL |
| 1.1 | 1.1.3 | May 1, 2023 | Jun 7, 2024 | 701 days past EOL | EOL |
| 1.2 | 1.2.3 | Aug 27, 2023 | Dec 15, 2024 | 510 days past EOL | EOL |
| 1.3 | 1.3.2 | Feb 7, 2024 | Feb 7, 2026 | 91 days past EOL | EOL |
| 1.4 LTS | 1.4.4 | Aug 15, 2024 | Aug 15, 2027 | 463 days remaining | Active |
| 1.5 | 1.5.2 | Oct 7, 2025 | Already EOL | Supported | Active |
When a Clamav version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Clamav should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →