ClamAV has rolled out versions 1.5.5 and 1.4.7 to address ten security flaws, many labeled high-severity, that could let attackers crash the antivirus scanner, trap its workers in endless loops, or abuse system resources through crafted files. These vulnerabilities were disclosed in a patch published on November 18, 2026 and affect components such as email parsing, document analysis, archive extraction, and executable unpacking.
Key Vulnerabilities & Affected Components
One of the most serious flaws, CVE-2026-76422, involves the Rust-to-C logging interface. Here, user-controlled text may be misinterpreted as a format string, creating possibilities for memory disclosure, crashes, or corruption. This bug is present as far back as version 0.105.0.
CVE-2026-76411 deals with URL normalization during email scanning. When ClamAV loads full-hash phishing entries, incorrect length handling can lead to a stack buffer overflow. Several unpackers are affected too—CVE-2026-76415 allows out-of-bounds heap reads in the yC unpacker, and CVE-2026-76421 and CVE-2026-76430 can trigger out-of-bounds writes when handling LZX data in CHM archives or UPX decompression and PE rebuilding.
Denial-of-service risks are also in the mix. CVE-2026-76414 may lead to infinite loops when processing CHM directory data, while CVE-2026-76416 can stall scan workers via malformed or invalid InstallShield archives. In document parsing, CVE-2026-76417 causes crashes by exhausting the stack with deeply nested OLE2 properties, and CVE-2026-76515 allows excessive CPU use by wrestling with directory chains in OLE2 files.
XAR archive extraction is also impacted by CVE-2026-76516, which allows crafted XAR files to drain temporary storage because extraction occurs before necessary limits are enforced.
Versions Affected & Mitigation Steps
All flaws impact ClamAV versions up to 1.5.4, with many stretching back to much older releases (e.g. OLE2 stack exhaustion dating to version 0.71). The release versions 1.5.5 and 1.4.7 (LTS) contain fixes across the board.
Users should update both the ClamAV engine and virus database—signature updates alone are not sufficient. New releases also restore functionality for ClamAV submissions, improve compatibility with OpenSSL 4, and refresh Rust dependencies. Container image maintainers (e.g. Alpine, Debian) should note that Docker Hub images may lag behind the official releases.
Analytical Perspective: These patches underline how antivirus software—specifically its parsers and archive handlers—remain a common attack surface. Because AV tools must examine untrusted inputs extensively, flaws in format parsing, recursive extraction, or directory walking often lead to crashes, resource exhaustion, or memory corruption. While there’s no current evidence these CVEs are being actively exploited, the age of some issues (parts of the code stretch back over a decade) suggests they could have gone unnoticed for a long time.