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. 1750 days past EOL — migrate to a supported version immediately.
EOL Date
Oct 29, 2021
1750 days past EOL
Latest Release
0.100.3
Standard release
Release Date
Apr 4, 2018
ClamAV 0.100 series
Lifecycle detail
ClamAV 0.100 was released on April 4, 2018 and support ended on October 29, 2021 — a supported lifespan of 3 years and 7 months, longer than the 3 years median for ClamAV releases. It was not an LTS release; ClamAV reserves longer patch windows for its LTS versions. The last patch it will ever receive is 0.100.3, published March 26, 2019 — 2 years and 7 months before support ended. It has been without security patches for 4 years and 10 months. 7 newer ClamAV releases have shipped since.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
Extended Support
Extended ClamAV 0.100 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
| 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 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.