CVE-2025-20260: Clamav remote code execution (CVSS 9.8)

Description

A vulnerability in the PDF scanning processes of ClamAV could allow an unauthenticated, remote attacker to cause a buffer overflow condition, cause a denial of service (DoS) condition, or execute arbitrary code on an affected device. This vulnerability exists because memory buffers are allocated incorrectly when PDF files are processed. 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 trigger a buffer overflow, likely resulting in the termination of the ClamAV scanning process and a DoS condition on the affected software. Although unproven, there is also a possibility that an attacker could leverage the buffer overflow to execute arbitrary code with the privileges of the ClamAV process.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Clamav≥ 1.2.0 < 1.4.3 · < 1.0.9

Remediation

Fixed in

Clamav≥ 1.4.3

Patch & vendor advisories

https://blog.clamav.net/2025/06/clamav-143-and-109-security-patch.html

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2025-20260 being actively exploited?

CVE-2025-20260 is not in the CISA KEV catalog. Its EPSS exploit probability is 1.63%.

How severe is CVE-2025-20260?

CVE-2025-20260 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 1.63% probability of exploitation.

Which products are affected by CVE-2025-20260?

Affected products include Clamav.

How do I fix CVE-2025-20260?

Upgrade affected software to a fixed version, for example Clamav 1.4.3 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-20260 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo