[From nobody Sun Aug 23 18:09:08 2026 Received: (at submit) by bugs.debian.org; 8 Aug 2026 16:34:26 +0000 X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02 (2024-03-25) on buxtehude.debian.org X-Spam-Level: X-Spam-Status: No, score=-4.0 required=4.0 tests=BAYES_00,SPF_HELO_NONE, SPF_PASS autolearn=ham autolearn_force=no version=4.0.1-bugs.debian.org_2005_01_02 X-Spam-Bayes: score:0.0000 Tokens: new, 31; hammy, 149; neutral, 48; spammy, 1. spammytokens:0.978-+--nbsp hammytokens:0.000-+--UD:security-tracker.debian.org, 0.000-+--securitytrackerdebianorg, 0.000-+--security-tracker.debian.org, 0.000-+--H*r:jmm, 0.000-+--sk:team@se Return-path: <jmm@inutil.org> Received: from inutil.org ([51.38.114.215]:45838 helo=vps-b7ad3695.vps.ovh.net) by buxtehude.debian.org with esmtp (Exim 4.96) (envelope-from <jmm@inutil.org>) id 1wsk08-002UEj-0f for submit@bugs.debian.org; Sat, 08 Aug 2026 16:34:26 +0000 Received: from soju.fritz.box (p5dc5d288.dip0.t-ipconnect.de [93.197.210.136]) by vps-b7ad3695.vps.ovh.net (Postfix) with ESMTPSA id 0E5AE644 for <submit@bugs.debian.org>; Sat, 8 Aug 2026 16:34:23 +0000 (UTC) Received: from jmm by soju.fritz.box with local (Exim 4.99.4) (envelope-from <jmm@soju.westfalen.local>) id 1wsk05-000000003Pq-3zsO for submit@bugs.debian.org; Sat, 08 Aug 2026 18:34:21 +0200 Date: Sat, 8 Aug 2026 18:34:21 +0200 To: submit@bugs.debian.org Subject: clamav: CVE-2026-20339 CVE-2026-20345 CVE-2026-20346 CVE-2026-20347 CVE-2026-20348 Message-ID: <andajfb666Hn9KRD@pisco.westfalen.local> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline From: =?UTF-8?Q?Moritz_M=C3=BChlenhoff?= <jmm@inutil.org> Delivered-To: submit@bugs.debian.org Source: clamav X-Debbugs-CC: team@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for clamav. CVE-2026-20339[0]: | A vulnerability in the PESpin file format parser of ClamAV could | allow an unauthenticated, remote attacker to cause a DoS condition | or possibly other expanded impacts as a result of memory | corruption on an affected device. This vulnerability is due to | improper boundary checks for content in PESpin files during | scanning, which may result in an integer overflow. An attacker could | exploit this vulnerability by submitting a crafted file that | contains PESpin content 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. CVE-2026-20345[1]: | A vulnerability in the GPT file format parser of ClamAV could allow | an unauthenticated, remote attacker to cause a DoS condition or | possibly other expanded impacts as a result of memory | corruption on an affected device. This vulnerability is due to | improper handling of an endian conversion operation, which may | result in an out-of-bounds buffer write. An attacker could exploit | this vulnerability by submitting a crafted GPT file 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. CVE-2026-20346[2]: | A vulnerability in the PDF file format parser of ClamAV could allow | an unauthenticated, remote attacker to cause a DoS condition or | possibly other expanded impacts as a result of memory | corruption on an affected device. This vulnerability is due to | improper boundary checks for content in PDF files during scanning, | which may result in an out-of-bounds buffer read. An attacker could | exploit this vulnerability by submitting a crafted PDF file 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. CVE-2026-20347[3]: | A vulnerability in the Mach-O file format parser of ClamAV could | allow an unauthenticated, remote attacker to cause a DoS condition | or possibly other expanded impacts as a result of memory | corruption on an affected device. This vulnerability is due to | improper boundary checks for content in Mach-O files during | scanning, which may result in an out-of-bounds buffer read. An | attacker could exploit this vulnerability by submitting a crafted | Mach-O file 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. CVE-2026-20348[4]: | A vulnerability in the XAR file format parser of ClamAV could allow | an unauthenticated, remote attacker to cause a DoS condition or | possibly other expanded impacts as a result of memory | corruption on an affected device. This vulnerability is due to | improper boundary checks for content in XAR files during scanning. | An attacker could exploit this vulnerability by submitting a crafted | file that contains XAR content 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. https://blog.clamav.net/2026/08/clamav-154-and-146-security-patch.html If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2026-20339 https://www.cve.org/CVERecord?id=CVE-2026-20339 [1] https://security-tracker.debian.org/tracker/CVE-2026-20345 https://www.cve.org/CVERecord?id=CVE-2026-20345 [2] https://security-tracker.debian.org/tracker/CVE-2026-20346 https://www.cve.org/CVERecord?id=CVE-2026-20346 [3] https://security-tracker.debian.org/tracker/CVE-2026-20347 https://www.cve.org/CVERecord?id=CVE-2026-20347 [4] https://security-tracker.debian.org/tracker/CVE-2026-20348 https://www.cve.org/CVERecord?id=CVE-2026-20348 Please adjust the affected versions in the BTS as needed. ]