CVE-2026-20217

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

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, ghsa, secondary
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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, resulting from 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 out-of-bounds buffer write. 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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
46%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 9, 2026

Advisory Details (1)

Auto-updated Jul 9, 2026
No patch confirmed yet.
generic

ClamAV Vulnerabilities Affecting Cisco Products: July 2026

https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-clamav-88cFYyxR

Vendor Advisories for CVE-2026-20217(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibclamav12 (1.5.3+dfsg-0ubuntu0.26.04.1) @ resolute2026-09-06ubuntu

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 rangeFixed inDependents
clamav0.103.10+dfsg-0+deb11u1 ... 1.4.5+dfsg-3 (57 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
clamav1.0.1+dfsg-2 ... 1.4.6+dfsg-1 (37 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
clamav1.4.3+dfsg-1 ... 1.4.6+dfsg-1 (8 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
clamav1.4.3+dfsg-1, 1.4.3+dfsg-2, 1.4.4+dfsg-1, 1.4.4+dfsg-21.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 12× in last 7d / 103× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 299 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-20217?
CVE-2026-20217 is a high vulnerability published on July 1, 2026. 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, resulting from memory corruption on an affected device. This vulnerability is due to improper boundary checks for content in…
When was CVE-2026-20217 disclosed?
CVE-2026-20217 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-20217 actively exploited?
CVE-2026-20217 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 54.5% of all scored CVEs.
What is the CVSS score of CVE-2026-20217?
CVE-2026-20217 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-20217?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-20217, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-20217?

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

Start Free Scan →Browse All CVEs