Skip to main content
Mallory
CriticalVulnerability

CVE-2026-58073: Unauthenticated Agent Impersonation and Credential Theft 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.
CVSS9.5Critical · v4
EPSS0.32%26th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-58073CWE-288 · Authentication Bypass Using an…

CVE-2026-58073 is an authentication bypass in Veeam Service Provider Console affecting version 9.2.1.33875 and all earlier version 9 builds. The console checks an agent GUID against a process-global logged-in-agent table without binding that login state to the certificate presented on the current connection. An unauthenticated attacker presenting a self-signed certificate with a parsable Veeam agent subject and the GUID of a currently connected agent can access an unrestricted agent channel and invoke IssueCertificateForAgent. This can disclose a PKCS#12 certificate bundle and private key signed by the console's trusted Veeam agent root CA, enabling agent impersonation. The vulnerability has a CVSS v4.0 score of 9.5 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 compromises the affected agent's authentication credentials and permits unauthorized impersonation within the Veeam management environment. When chained with CVE-2026-58072, the acquired agent certificate can enable arbitrary file writes on the management server and remote code execution. Code execution is a consequence of the combined vulnerabilities, not an independently established capability of CVE-2026-58073. Certificates obtained before patching remain a security risk because upgrading does not revoke them.

Mitigation

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

Restrict access to the agent communication channel to legitimate agent networks wherever possible. Account for direct agent connections on TCP/9999 and, where applicable, connectivity through Veeam Cloud Connect gateways on TCP/6180. Monitor for certificate-validation failures followed by channel replacement and an IssueCertificateForAgent call associated with the same agent GUID. These measures reduce exposure and support detection but do not replace upgrading.

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. The fixed release requires the current connection's certificate thumbprint to match the certificate recorded for the agent login. Investigate potential exploitation before the upgrade, since patching does not invalidate previously issued attacker-held certificates. Contact Veeam Support if logs indicate compromised agent certificates.

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-58073 exploited in the wild?
As of Nov 16, 2026, Mallory has no reports of CVE-2026-58073 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-58073?
As of Nov 16, 2026, Mallory has found no public exploit for CVE-2026-58073.
Is there a patch for CVE-2026-58073?
Upgrade Veeam Service Provider Console to version 9.3.0.35057 or later; no 9.2.x backport is available. The fixed release requires the current connection's certificate thumbprint to match the certificate recorded for the agent login.
How severe is CVE-2026-58073?
CVE-2026-58073 has a CVSS v4 score of 9.5 (Critical) and an EPSS score of 0.32% (26th percentile) as of Nov 16, 2026.
Activity feed

Recent activity

19 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
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 activity9Community discussion across Reddit, Mastodon, and other social sources.