ClamAV PESpin File Format Processing Integer Overflow Vulnerability
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.
- Published
- Aug 7, 2026
- Updated
- Aug 11, 2026
- EPSS
- 0.5% · 38th percentile
- CWE
- CWE-190
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · cisco
- 7.5
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (cisco). Independent of NVD's CPE analysis and usually ahead of it.
Cisco Cisco Secure Endpoint
- 7.0.5, 6.2.19, 7.3.3, 7.2.13, 6.1.5, 6.3.1, 6.2.5, 7.3.5, 6.2.1, 7.2.7, 7.1.1, 6.3.5 … (+28)affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | clamav | all versions | — |
| Debian:14 | clamav | before 1.4.6+dfsg-1 | 1.4.6+dfsg-1 |
| openSUSE:Leap 16.0 | clamav | before 1.5.4-160000.1.1 | 1.5.4-160000.1.1 |
| openSUSE:Tumbleweed | clamav | before 1.5.4-1.1 | 1.5.4-1.1 |
| SUSE:Linux Enterprise Micro 5.5 | clamav | before 1.5.4-150400.13.11.1 | 1.5.4-150400.13.11.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP7 | clamav | before 1.5.4-150600.18.31.1 | 1.5.4-150600.18.31.1 |
| SUSE:Linux Enterprise Server 12 SP5-LTSS | clamav | before 1.5.4-3.59.1 | 1.5.4-3.59.1 |
| SUSE:Linux Enterprise Server 16.0 | clamav | before 1.5.4-160000.1.1 | 1.5.4-160000.1.1 |
Same product
cisco: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-20347ClamAV Mach-O File Format Processing Memory Corruption Vulnerability30Monitor
- CVE-2026-20346ClamAV PDF File Format Processing Memory Corruption Vulnerability30Monitor
- CVE-2026-20345ClamAV GPT File Format Processing Memory Corruption Vulnerability30Monitor
- CVE-2026-20338ClamAV ZIP File Format Processing Memory Corruption Vulnerability30Monitor
- CVE-2026-20337ClamAV ZIP File Format Processing Memory Corruption Vulnerability30Monitor
- CVE-2026-20031ClamAV CSS Image Parsing Error Handling Denial of Service Vulnerability21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| azl3 clamav 1.5.3-1 on Azure Linux 3.0 | 1.5.4-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:clamav | 1.4.6+dfsg-1 · Debian:14 | Package registry (OSV) |
| opensuse:clamav | 1.5.4-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:clamav | 1.5.4-160000.1.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-190 · Integer Overflow or WraparoundCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.