CVE-2026-20215

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-01. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-41083 (ENISA EUVD) · GHSA-6gff-7f37-2v35 (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A vulnerability in the 7z 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 7z 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 7z 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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
47th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 1, 2026

Last Modified

October 25, 2026

Advisory Details (1)

Auto-updated Jul 6, 2026
Patch available.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibclamav12 (1.5.3+dfsg-0ubuntu0.26.04.1) @ resolute2026-10-25ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
clamav0.103.10+dfsg-0+deb11u1 ... 1.4.5+dfsg-3 (57 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
clamav1.0.1+dfsg-2 ... 1.4.6+dfsg-1 (37 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
clamav1.4.3+dfsg-1 ... 1.4.6+dfsg-1 (8 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
clamav1.4.3+dfsg-1, 1.4.3+dfsg-2, 1.4.4+dfsg-1, 1.4.4+dfsg-2
  • every version up to 1.4.5+dfsg-1: fixed in 1.4.5+dfsg-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 14× in last 7d / 44× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 348 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 248 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  2. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  3. 2026-10-25 17:28 UTCEG score recompute
  4. 2026-10-25 17:28 UTCVendor advisory
  5. 2026-10-25 17:28 UTCGHSA enrichmentGHSA-6gff-7f37-2v35 · GitHub severity HIGH · GitHub CVSS 7.5
  6. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  7. 2026-10-25 14:44 UTCEG score recompute
  8. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  9. 2026-10-24 11:30 UTCEG score recompute
  10. 2026-10-24 11:30 UTCVendor advisory
  11. 2026-10-24 11:29 UTCGHSA enrichmentGHSA-6gff-7f37-2v35 · GitHub severity HIGH · GitHub CVSS 7.5
  12. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  13. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  14. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  15. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  16. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  17. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  18. 2026-10-18 03:57 UTCEG score recompute
  19. 2026-10-17 17:38 UTCEG score recompute
  20. 2026-10-17 17:38 UTCVendor advisory
  21. 2026-10-17 17:38 UTCGHSA enrichmentGHSA-6gff-7f37-2v35 · GitHub severity HIGH · GitHub CVSS 7.5
  22. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  23. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  24. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  25. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.6% · 46th percentile
Show 75 more
  1. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  2. 2026-10-13 16:24 UTCOSV refresh
  3. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  4. 2026-10-12 16:24 UTCEG score recompute
  5. 2026-10-11 20:06 UTCEG score recompute
  6. 2026-10-11 17:19 UTCEG score recompute
  7. 2026-10-11 14:51 UTCEG score recompute
  8. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  9. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  10. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  11. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  12. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  13. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  14. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  15. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  16. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  17. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  18. 2026-09-29 15:21 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  19. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  20. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  21. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  22. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  23. 2026-09-24 14:03 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  24. 2026-09-23 06:51 UTCEG score recompute
  25. 2026-09-23 06:51 UTCVendor advisory
  26. 2026-09-23 06:51 UTCGHSA enrichmentGHSA-6gff-7f37-2v35 · GitHub severity HIGH · GitHub CVSS 7.5
  27. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  28. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  29. 2026-09-18 06:32 UTCEG score recompute
  30. 2026-09-18 06:32 UTCVendor advisory
  31. 2026-09-18 06:32 UTCGHSA enrichmentGHSA-6gff-7f37-2v35 · GitHub severity HIGH · GitHub CVSS 7.5
  32. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  33. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  34. 2026-09-14 00:22 UTCEG score recompute
  35. 2026-09-14 00:22 UTCVendor advisory
  36. 2026-09-14 00:22 UTCGHSA enrichmentGHSA-6gff-7f37-2v35 · GitHub severity HIGH · GitHub CVSS 7.5
  37. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  38. 2026-09-13 09:08 UTCEG score recompute
  39. 2026-09-13 09:08 UTCVendor advisory
  40. 2026-09-13 09:08 UTCGHSA enrichmentGHSA-6gff-7f37-2v35 · GitHub severity HIGH · GitHub CVSS 7.5
  41. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  42. 2026-09-12 14:42 UTCEG score recompute
  43. 2026-09-12 14:42 UTCVendor advisory
  44. 2026-09-12 14:42 UTCGHSA enrichmentGHSA-6gff-7f37-2v35 · GitHub severity HIGH · GitHub CVSS 7.5
  45. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  46. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  47. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  48. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  49. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  50. 2026-09-06 15:57 UTCEG score recompute
  51. 2026-09-06 15:57 UTCVendor advisory
  52. 2026-09-06 15:57 UTCGHSA enrichmentGHSA-6gff-7f37-2v35 · GitHub severity HIGH · GitHub CVSS 7.5
  53. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  54. 2026-09-06 02:17 UTCEG score recompute
  55. 2026-09-06 02:17 UTCVendor advisory
  56. 2026-09-06 02:17 UTCGHSA enrichmentGHSA-6gff-7f37-2v35 · GitHub severity HIGH · GitHub CVSS 7.5
  57. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  58. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  59. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  60. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  61. 2026-08-31 00:51 UTCEG score recompute
  62. 2026-08-31 00:51 UTCVendor advisory
  63. 2026-08-31 00:51 UTCGHSA enrichmentGHSA-6gff-7f37-2v35 · GitHub severity HIGH · GitHub CVSS 7.5
  64. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  65. 2026-08-30 11:45 UTCEG score recompute
  66. 2026-08-30 11:45 UTCVendor advisory
  67. 2026-08-30 11:45 UTCGHSA enrichmentGHSA-6gff-7f37-2v35 · GitHub severity HIGH · GitHub CVSS 7.5
  68. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  69. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  70. 2026-08-27 22:26 UTCEG score recompute
  71. 2026-08-27 22:26 UTCVendor advisory
  72. 2026-08-27 22:26 UTCGHSA enrichmentGHSA-6gff-7f37-2v35 · GitHub severity HIGH · GitHub CVSS 7.5
  73. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  74. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  75. 2026-08-25 16:21 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-20215?
CVE-2026-20215 is a high-severity vulnerability; its CVE record was published on July 1, 2026. A vulnerability in the 7z 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 7z files…
When was the CVE record for CVE-2026-20215 published?
The CVE record for CVE-2026-20215 was published on July 1, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 25, 2026; the record at its source may have been updated since.
Is CVE-2026-20215 actively exploited?
CVE-2026-20215 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-20215?
CVE-2026-20215 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-20215?
A fix for CVE-2026-20215 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-20215 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-20215

Explore →

Is Your Infrastructure Affected by CVE-2026-20215?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.