Veeam is widely used for enterprise backup; unauthenticated DoS against Service Provider Console can disrupt backup/restore operations across customers and managed environments.
CVE-2026-58067
Unauthenticated remote memory exhaustion in Veeam Service Provider Console causing DoS.
Is CVE-2026-58067 being exploited?
Not confirmed. CVE-2026-58067 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.39% probability of exploitation in the next 30 days.
How severe is CVE-2026-58067?
CVE-2026-58067 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-58067?
Not known from our data. No patch reference has been recorded for CVE-2026-58067, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-58067 affect?
CVE-2026-58067 affects Veeam Service Provider Console, Veeam Cloud Service Provider (VCSP) environments. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-58067?
Restrict access to console, apply vendor patch/mitigation when released, monitor for abnormal memory/availability.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attacker can exhaust host memory remotely, causing denial of service and disruption of backup management and restore operations.
Immediate action required
- affected< 9.3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.