CVE-2026-58067

HIGHPre-NVD 8.78.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 77% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A vulnerability in Veeam Service Provider Console allowing an unauthenticated attacker to exhaust host memory and cause adenial of service.

CVSS v3
8.7
EG Score
8.7(medium)
EG Risk
54(Track)
EG Risk 54/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
Severity87% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

August 4, 2026

Last Modified

August 4, 2026

Advisory Details (1)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

KB4893: Vulnerabilities Resolved in Veeam Service Provider Console 9.3

https://www.veeam.com/kb4893

Vendor Advisories for CVE-2026-58067(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 27× in last 7d / 67× 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-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 21:41 UTCGHSA enrichment
  3. 2026-08-20 10:19 UTCGHSA enrichment
  4. 2026-08-19 22:57 UTCEG score recompute
  5. 2026-08-19 22:57 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 11:35 UTCGHSA enrichment
  8. 2026-08-19 00:11 UTCEG score recompute
  9. 2026-08-19 00:11 UTCGHSA enrichment
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-18 12:49 UTCGHSA enrichment
  12. 2026-08-18 00:59 UTCEG score recompute
  13. 2026-08-18 00:59 UTCGHSA enrichment
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 13:35 UTCGHSA enrichment
  16. 2026-08-17 02:13 UTCEG score recompute
  17. 2026-08-17 02:13 UTCGHSA enrichment
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 14:51 UTCGHSA enrichment
  20. 2026-08-16 03:29 UTCEG score recompute
  21. 2026-08-16 03:29 UTCGHSA enrichment
  22. 2026-08-16 02:14 UTCEPSS rescore
  23. 2026-08-15 16:07 UTCGHSA enrichment
  24. 2026-08-15 04:45 UTCEG score recompute
  25. 2026-08-15 04:45 UTCGHSA enrichment
Show 42 more
  1. 2026-08-15 01:30 UTCEPSS rescore
  2. 2026-08-14 17:22 UTCGHSA enrichment
  3. 2026-08-14 05:52 UTCEG score recompute
  4. 2026-08-14 05:52 UTCGHSA enrichment
  5. 2026-08-13 22:00 UTCEPSS rescore
  6. 2026-08-13 18:30 UTCGHSA enrichment
  7. 2026-08-13 07:08 UTCGHSA enrichment
  8. 2026-08-12 19:42 UTCEG score recompute
  9. 2026-08-12 19:42 UTCGHSA enrichment
  10. 2026-08-12 13:51 UTCEPSS rescore
  11. 2026-08-12 08:20 UTCGHSA enrichment
  12. 2026-08-11 20:57 UTCEG score recompute
  13. 2026-08-11 20:57 UTCGHSA enrichment
  14. 2026-08-11 09:35 UTCEG score recompute
  15. 2026-08-11 09:35 UTCGHSA enrichment
  16. 2026-08-11 00:00 UTCEPSS rescore
  17. 2026-08-10 22:13 UTCGHSA enrichment
  18. 2026-08-10 10:50 UTCGHSA enrichment
  19. 2026-08-09 23:28 UTCEG score recompute
  20. 2026-08-09 23:28 UTCGHSA enrichment
  21. 2026-08-09 13:46 UTCEPSS rescore
  22. 2026-08-09 12:06 UTCGHSA enrichment
  23. 2026-08-09 00:44 UTCEG score recompute
  24. 2026-08-09 00:44 UTCGHSA enrichment
  25. 2026-08-08 16:37 UTCEPSS rescore
  26. 2026-08-08 13:22 UTCGHSA enrichment
  27. 2026-08-08 01:59 UTCEG score recompute
  28. 2026-08-08 01:59 UTCGHSA enrichment
  29. 2026-08-07 14:37 UTCGHSA enrichment
  30. 2026-08-07 03:15 UTCGHSA enrichment
  31. 2026-08-06 15:53 UTCEG score recompute
  32. 2026-08-06 15:53 UTCGHSA enrichment
  33. 2026-08-06 13:47 UTCEPSS rescore
  34. 2026-08-06 04:31 UTCEG score recompute
  35. 2026-08-06 04:31 UTCGHSA enrichment
  36. 2026-08-05 19:17 UTCEPSS rescore
  37. 2026-08-05 17:09 UTCGHSA enrichment
  38. 2026-08-05 05:47 UTCGHSA enrichment
  39. 2026-08-04 18:25 UTCEG score recompute
  40. 2026-08-04 17:23 UTCEG score recompute
  41. 2026-08-04 16:28 UTCEG score recompute
  42. 2026-08-04 16:26 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-58067?
CVE-2026-58067 is a high vulnerability published on August 4, 2026. A vulnerability in Veeam Service Provider Console allowing an unauthenticated attacker to exhaust host memory and cause adenial of service.
When was CVE-2026-58067 disclosed?
CVE-2026-58067 was first published in the National Vulnerability Database on August 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58067 actively exploited?
CVE-2026-58067 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 77.3% of all scored CVEs.
What is the CVSS score of CVE-2026-58067?
CVE-2026-58067 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-58067?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58067, 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-58067

Explore →

Is Your Infrastructure Affected by CVE-2026-58067?

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

Start Free Scan →Browse All CVEs