HIGH 7.5

CVE-2026-20214: ClamAV FSG Parser Out-of-Bounds Write DoS

ClamAV, a widely deployed open-source antivirus engine used in products like Cisco Secure Endpoint, contains a flaw in how it parses FSG-compressed executable files. An attacker can craft a malicious FSG file that triggers an out-of-bounds memory write when scanned, crashing the scanning process and disrupting threat detection. This is a network-reachable denial-of-service vulnerability requiring no authentication or user interaction.

Source data · NVD / CISA · public domain

CVSS
3.1 · 7.5 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weaknesses (CWE)
CWE-120
Affected products
4 configuration(s)
Published / Modified
2026-07-01 / 2026-07-09

NVD description (verbatim)

A vulnerability in the FSG file format parser of ClamAV could allow an unauthenticated, remote attacker to cause a DoS condition, or possibly other expanded impacts, resulting from memory corruption on an affected device. This vulnerability is due to improper boundary checks for content in FSG files during scanning, which may result in an out-of-bounds buffer write. An attacker could exploit this vulnerability by submitting a crafted file that contains portable executable content compressed with FSG to be scanned by ClamAV on an affected device. A successful exploit could allow the attacker to cause the ClamAV scanning process to terminate, resulting in a DoS condition on the affected software.

1 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-20214 stems from inadequate boundary validation in ClamAV's FSG file format parser. The vulnerability manifests as an out-of-bounds buffer write (CWE-120) when processing portable executable content compressed with FSG compression. The flaw allows remote unauthenticated attackers to submit crafted files that corrupt memory in the scanning process, leading to process termination. The CVSS 3.1 score of 7.5 (HIGH) reflects the high availability impact and low attack complexity, though confidentiality and integrity are not directly affected by this specific flaw path.

Business impact

Organizations relying on ClamAV for email gateway scanning, file server protection, or endpoint defense face potential service disruptions. Successful exploitation causes the scanner to crash, creating a window where malware may evade detection. In regulated environments (finance, healthcare, government), sustained scanner unavailability can trigger compliance violations and audit findings. For MSPs and security appliance vendors embedding ClamAV, this vulnerability directly affects customer SLAs and trust.

Affected systems

ClamAV is directly affected. Cisco Secure Endpoint (all versions mentioned in the vulnerability record) incorporates ClamAV for on-access and on-demand scanning. Any deployment of ClamAV—whether standalone on Linux/Unix servers, integrated into mail gateways, or bundled in third-party security products—is in scope. Organizations should verify whether their endpoint, gateway, or server protection solutions depend on ClamAV.

Exploitability

Exploitation is straightforward: an attacker crafts an FSG-compressed portable executable file and submits it for scanning (via email, file upload, malware honeypot, or direct file placement on a monitored system). No authentication, user interaction, or special network position is required. The attack succeeds if the vulnerable ClamAV process is accessible and actively scanning user-controlled files. Public exploit code has not been reported, but the vulnerability is not complex to weaponize given the detailed technical description.

Remediation

Apply the latest patched version of ClamAV from the official ClamAV project repository. Verify the patch version against Cisco and ClamAV security advisories to confirm the FSG parser boundary check has been corrected. For Cisco Secure Endpoint users, updates are typically delivered through the Cisco security update channels; prioritize deployment in environments scanning untrusted files. As a temporary mitigation, disable FSG decompression in ClamAV configuration if feasible, though this may reduce malware detection capability.

Patch guidance

Check the ClamAV project's official release notes and security advisories for the version that remediates this boundary check issue. Cisco customers should consult the Cisco Security Advisory related to CVE-2026-20214 for Secure Endpoint patch versions and deployment procedures. Test patches in a non-production environment first, especially if ClamAV is integrated into critical scanning infrastructure. Update the malware signature database alongside any engine patches. Establish a schedule to verify that all downstream products and integrations consuming ClamAV are updated.

Detection guidance

Monitor for unexpected ClamAV process crashes or high CPU spikes followed by scanner termination in antivirus logs and system event logs. Watch for malformed FSG-compressed files in network traffic or file repositories (FSG files typically have specific magic bytes and header patterns). Implement file type restrictions at ingestion points if FSG is not a legitimate business format. Review ClamAV logs for parsing errors or exceptions when processing attachments or uploaded files. Host-based intrusion detection can flag segmentation faults or abnormal process termination of the scanner daemon.

Why prioritize this

This vulnerability merits immediate attention because it directly disrupts the availability of a security control (malware scanning) through a network-reachable, unauthenticated attack. The HIGH CVSS score and ease of exploitation outweigh the fact that it is not yet in CISA's KEV catalog. Organizations in regulated industries or those handling sensitive data cannot tolerate scanner unavailability. Although the vulnerability does not leak data or corrupt files directly, its denial-of-service impact on threat detection creates a critical security gap.

Risk score, explained

The CVSS 3.1 score of 7.5 reflects: network-based attack vector (AV:N), low attack complexity (AC:L), no privilege or user interaction required (PR:N/UI:N), and high impact on availability (A:H). The lack of confidentiality and integrity impact keeps the score below critical range. However, in the context of a malware scanner, availability is the primary function; disrupting it elevates real-world risk beyond the numeric score. Organizations should consider local context (how exposed is the ClamAV process to untrusted input) when determining internal priority.

Frequently asked questions

What file types trigger this vulnerability?

Portable executable files (PE, EXE, DLL, etc.) that are compressed with FSG compression. FSG is a file packer often used by malware authors, so ClamAV's parser is essential for detection. A crafted malicious FSG-compressed PE file submitted for scanning will trigger the out-of-bounds write.

Does this vulnerability allow code execution, or just denial of service?

The described vulnerability vector is denial of service (process crash). The memory corruption is an out-of-bounds buffer write, which in principle could potentially be leveraged for code execution by a sophisticated attacker; however, the official vulnerability description and CVSS vector limit the impact to availability (A:H, with C:N and I:N). Always verify against vendor advisories for any updates or corrections to the impact assessment.

Are all versions of ClamAV affected, or only certain releases?

The vulnerability record does not specify exact affected versions. Consult the ClamAV project's security advisories and the Cisco Security Advisory for CVE-2026-20214 to determine which versions are vulnerable and which patches resolve the issue. Assume all recent versions are at risk until patched.

Can I disable FSG decompression to mitigate this without patching?

Yes, in some ClamAV deployments you can modify the configuration to skip FSG decompression. However, this reduces malware detection capability, as FSG-packed malware is common. Disabling FSG should be a temporary measure only, and you should plan to patch and re-enable the feature immediately.

This analysis is provided for informational purposes and is based on the vulnerability record published on 2026-07-01, last modified 2026-07-09. SEC.co makes no warranty regarding the accuracy, completeness, or timeliness of this information. Readers are responsible for verifying all technical details, patch availability, and affected product versions against official vendor advisories before taking remediation action. Patch versions, workarounds, and support timelines are the responsibility of the vendor and should be obtained directly from ClamAV and Cisco security channels. This explainer does not constitute professional security advice; consult your organization's security team or vendor support for deployment decisions. Source: NVD (public-domain), retrieved 2026-08-10. Analysis generated by SEC.co (claude-haiku-4-5).