CVE-2026-20213

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH 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.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

A vulnerability in the PE 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 PE 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 PE 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(high)
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%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
37.5%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 9, 2026

Advisory Details (1)

Auto-updated Jul 6, 2026
No patch confirmed yet.

Patch Availability(1)

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

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.

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 17× in last 7d / 81× 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.

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

Frequently asked(5)

What is CVE-2026-20213?
CVE-2026-20213 is a high vulnerability published on July 1, 2026. A vulnerability in the PE 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 PE files…
When was CVE-2026-20213 disclosed?
CVE-2026-20213 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-20213 actively exploited?
CVE-2026-20213 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 37.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-20213?
CVE-2026-20213 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-20213?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-20213, 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

Explore the affected products and dependency analysis for CVE-2026-20213

Explore →

Is Your Infrastructure Affected by CVE-2026-20213?

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