Skip to main content
Mallory
HighVulnerability

CVE-2026-58067: Unauthenticated Memory Exhaustion in Veeam Service Provider Console

Published Aug 4, 2026 · Updated 2 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.7High · v4
EPSS0.45%39th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-58067CWE-789 · Memory Allocation with Excessive…

CVE-2026-58067 is an unauthenticated memory-exhaustion vulnerability in Veeam Service Provider Console. Unbounded buffering of inbound packets on the agent communication channel allows a remote attacker to exhaust host memory and cause denial of service. Affected releases include version 9.2.1.33875 and earlier version 9 builds. The vulnerability has a CVSS v4.0 score of 8.7 and is fixed in version 9.3.0.35057.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can exhaust the affected host's memory and disrupt Veeam Service Provider Console availability. The vulnerability has a high availability impact; no direct confidentiality or integrity impact is identified.

Mitigation

If you can’t patch tonight, do this now.

Until the upgrade is completed, restrict network access to the agent communication channel to legitimate agent networks where feasible, including TCP/9999 and any applicable Cloud Connect gateway exposure on TCP/6180. This reduces exposure but does not correct the vulnerability. No vendor-provided temporary workaround is specified.

Remediation

Patch, then assume compromise.

Upgrade Veeam Service Provider Console to version 9.3.0.35057 or later. No 9.2.x backport is available.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
FAQ

Frequently asked questions

Is CVE-2026-58067 exploited in the wild?
As of Nov 16, 2026, Mallory has no reports of CVE-2026-58067 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-58067?
As of Nov 16, 2026, Mallory has found no public exploit for CVE-2026-58067.
Is there a patch for CVE-2026-58067?
Upgrade Veeam Service Provider Console to version 9.3.0.35057 or later. No 9.2.x backport is available.
How severe is CVE-2026-58067?
CVE-2026-58067 has a CVSS v4 score of 8.7 (High) and an EPSS score of 0.45% (39th percentile) as of Nov 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.