CVE-2026-20031VulnerabilityPublished 20 Apr 2026Updated 17 Sep 2026

SUSE · Security update for clamav

Affects SUSESource GCVE Database

Compare

Authoritative record:CVE-2026-20031· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium.

Data as of 31 Oct 2026, 20:20 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
CiscoCisco Secure Endpoint	Affected 1.1.0 – 8.4.5.30483 162 affected builds	Fixed in–

AI-suggested

Apply the update to ClamAV version 1.5.2 or later, which includes the fix for CVE-2026-20031. This update also addresses other stability and security improvements. No additional mitigation steps are indicated.

Description

A security update for ClamAV addresses CVE-2026-20031, which involves improper error handling in the HTML CSS module when splitting UTF-8 strings. This flaw can cause denial of service conditions via a crafted HTML file. The update also includes fixes for non-security issues and upgrades dependencies to resolve other advisories and stability problems.

Impact

The vulnerability can cause denial of service conditions in ClamAV when processing maliciously crafted HTML files. There is no indication of code execution or data compromise. No known exploits are reported in the wild.

Summary

CVE-2026-20031 is a vulnerability in ClamAV 1.5.2 related to improper error handling in the HTML CSS module during UTF-8 string splitting. This can lead to denial of service conditions triggered by specially crafted HTML files. The update to ClamAV 1.5.2 fixes this issue along with other non-security improvements such as support for transactional updates, fixes for infinite loops in JPEG scanning, and dependency upgrades addressing other advisories.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Sep 2026, 02:29 UTC

Technical details

References

Community reviews

Related threats