ClamAV vulnerabilities: known CVEs & security history
Cisco · Security / Antivirus · 7 tracked CVEs · 0 actively exploited · updated August 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all ClamAV release lines — 7 in total. A CVE here doesn't mean your version is affected — check ClamAV's current status and the safe version to run.
Known ClamAV CVEs
Actively-exploited and most-severe first. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2026-20244 | high | 7.5 | 0% | 2026 |
| CVE-2026-20243 | high | 7.5 | 0% | 2026 |
| CVE-2026-20217 | high | 7.5 | 0% | 2026 |
| CVE-2026-20216 | high | 7.5 | 0% | 2026 |
| CVE-2026-20215 | high | 7.5 | 0% | 2026 |
| CVE-2026-20214 | high | 7.5 | 0% | 2026 |
| CVE-2026-20213 | high | 7.5 | 0% | 2026 |
Is my ClamAV version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your ClamAV version → · Monitor ClamAV for new CVEs →
ClamAV vulnerabilities — frequently asked
How many known vulnerabilities does ClamAV have?
IsItPatched tracks 7 CVEs for ClamAV. 0 are critical-severity and 7 high-severity. These span every release line — what matters is whether the version you run is affected.
Does ClamAV have any actively-exploited vulnerabilities?
None of ClamAV's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.
What is the most severe ClamAV vulnerability?
Among tracked issues, CVE-2026-20244 (HIGH, CVSS 7.5) ranks highest — a Buffer overflow weakness.
Is ClamAV safe to use?
It depends on the version. The latest supported ClamAV release (1.5.3) clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: ClamAV security status · ClamAV end-of-life · actively-exploited CVEs. Always verify against Cisco's advisories — see our disclaimer.