Clamav 0.100 · Version Status

Clamav 0.100 End of Life Date

Clamav 0.100 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

Clamav 0.100 is past end of life. This version no longer receives security patches. 1653 days past EOL — migrate to a supported version immediately.
EOL Date
Oct 29, 2021
1653 days past EOL
Latest Release
0.100.3
Standard release
Release Date
Apr 4, 2018
Clamav 0.100 series
← Clamav 0.99 All Clamav versions Clamav 0.101 →
Recommended upgrade path
Clamav 1.5
Latest release: 1.5.2 · EOL: Supported
View full Clamav timeline →
All Clamav Versions
VersionLatestEOL DateStatus
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 0.100 end of life mean?

When Clamav 0.100 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 0.100 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 0.100 reach end of life?
Clamav 0.100 reached end of life on October 29, 2021. This version is no longer receiving security patches.
Is Clamav 0.100 still supported?
No. Clamav 0.100 reached end of life on October 29, 2021 and is no longer receiving security patches.
What should I upgrade to from Clamav 0.100?
The recommended upgrade from Clamav 0.100 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 0.100 past EOL?
When Clamav 0.100 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.
Data from endoflife.date API · Generated at build time · How we source data →