Clamav 1.3 · Version Status
Clamav 1.3 End of Life Date
Clamav 1.3 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Clamav 1.3 is past end of life. This version no longer receives security patches. 91 days past EOL — migrate to a supported version immediately.
EOL Date
Feb 7, 2026
91 days past EOL
Latest Release
1.3.2
Standard release
Release Date
Feb 7, 2024
Clamav 1.3 series
| Version | Latest | EOL Date | Status |
|---|
| 0.99 |
0.99.4 |
Mar 1, 2021 |
EOL |
| 0.100 |
0.100.3 |
Oct 29, 2021 |
EOL |
| 0.101 |
0.101.5 |
Jan 3, 2022 |
EOL |
| 0.102 |
0.102.4 |
Jan 3, 2022 |
EOL |
| 0.103 LTS |
0.103.12 |
Sep 14, 2024 |
EOL |
| 0.104 |
0.104.4 |
Mar 28, 2023 |
EOL |
| 0.105 |
0.105.2 |
Sep 1, 2023 |
EOL |
| 1.0 LTS |
1.0.9 |
Nov 28, 2025 |
EOL |
What does Clamav 1.3 end of life mean?
When Clamav 1.3 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Clamav 1.3 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Clamav 1.5 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Clamav 1.3 reach end of life?
Clamav 1.3 reached end of life on February 7, 2026. This version is no longer receiving security patches.
Is Clamav 1.3 still supported?
No. Clamav 1.3 reached end of life on February 7, 2026 and is no longer receiving security patches.
What should I upgrade to from Clamav 1.3?
The recommended upgrade from Clamav 1.3 is
Clamav 1.5 — the latest actively supported version. Check the
Clamav full timeline for all supported versions.
What are the security risks of running Clamav 1.3 past EOL?
When Clamav 1.3 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Clamav should migrate immediately or implement compensating controls.