<Vulnerability name="CVE-2026-20214">
    <DocumentDistribution xml:lang="en">Copyright © 2012 Red Hat, Inc. All rights reserved.</DocumentDistribution>
    <ThreatSeverity>Important</ThreatSeverity>
    <PublicDate>2026-07-01T16:27:33</PublicDate>
    <Bugzilla id="2496096" url="https://bugzilla.redhat.com/show_bug.cgi?id=2496096" xml:lang="en:us">
clamav: ClamAV: Denial of Service via crafted FSG file parsing
    </Bugzilla>
    <CVSS3 status="draft">
        <CVSS3BaseScore>7.5</CVSS3BaseScore>
        <CVSS3ScoringVector>CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H</CVSS3ScoringVector>
    </CVSS3>
    <CWE>CWE-787</CWE>
    <Details xml:lang="en:us" source="Mitre">
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.
    </Details>
    <Details xml:lang="en:us" source="Red Hat">
A flaw was found in ClamAV. An unauthenticated, remote attacker could exploit a vulnerability in the FSG file format parser by submitting a specially crafted file for scanning. This improper handling of FSG files can lead to an out-of-bounds buffer write, causing memory corruption. A successful exploit results in a Denial of Service (DoS) condition, terminating the ClamAV scanning process.
    </Details>
    <Statement xml:lang="en:us">
This flaw in ClamAV is rated as Important because an unauthenticated, remote attacker can trigger a denial of service by submitting a specially crafted FSG file for scanning. This can lead to memory corruption and terminate the ClamAV scanning process, impacting services relying on ClamAV for content inspection.
    </Statement>
    <Mitigation xml:lang="en:us">
To reduce the attack surface, restrict network access to the ClamAV daemon (clamd) to trusted clients only. This can be achieved by configuring firewall rules to limit connections to the port clamd listens on. For example, using `firewalld`:
`firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="&lt;TRUSTED_IP_ADDRESS&gt;" port port="3310" protocol="tcp" accept'`
`firewall-cmd --reload`
Replace `&lt;TRUSTED_IP_ADDRESS&gt;` with the IP address or network range of trusted clients. This mitigation may impact legitimate scanning operations if not configured correctly. A restart of the `clamd` service may be required for changes to take full effect.
    </Mitigation>
    <References xml:lang="en:us">
https://www.cve.org/CVERecord?id=CVE-2026-20214
https://nvd.nist.gov/vuln/detail/CVE-2026-20214
https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-clamav-88cFYyxR
    </References>
</Vulnerability>