Executive Summary
In August 2026, Veeam disclosed critical vulnerabilities CVE-2026-58073 (CVSS 9.5) and CVE-2026-58072 (CVSS 9.0) affecting Veeam Service Provider Console versions 9.2.1 and earlier. The vulnerabilities allow unauthenticated attackers to impersonate backup agents, obtain legitimate certificates, and write arbitrary files to achieve remote code execution. This attack chain targets the multi-tenant console that managed service providers use to control backups across all customer environments, making it a high-value target. Bishop Fox demonstrated end-to-end exploitation and published detection tools. Organizations must immediately upgrade to version 9.3.0, as no backport fixes are available for earlier versions.
This incident highlights the growing threat to backup infrastructure as ransomware groups increasingly target backup systems to prevent recovery operations. With managed service providers becoming prime targets due to their multi-tenant access, authentication bypass vulnerabilities in critical infrastructure components represent existential risks to business continuity across entire customer portfolios.
Why This Matters Now
Backup infrastructure has become a primary ransomware target as attackers seek to prevent recovery operations. With MSPs managing critical systems for multiple organizations, authentication bypass vulnerabilities in backup consoles create cascading risks across entire customer bases, making immediate patching essential for business continuity.
Attack Path Analysis
Attackers exploited critical authentication flaws in Veeam Service Provider Console to impersonate legitimate backup agents, steal valid certificates, and achieve remote code execution on the management server controlling multiple customer environments. The attack leveraged unauthenticated access to agent channels, certificate theft, arbitrary file writes, and web shell deployment for persistent access to the backup control plane.
Kill Chain Progression
This analysis maps confirmed threat intelligence to the full cloud kill chain to show where defensive gaps would emerge as an attack progresses.
Initial Compromise
Description
Attackers exploited CVE-2026-58073 by connecting to TCP/9999 with self-signed certificates containing known agent GUIDs, bypassing authentication due to weak GUID-only validation that didn't verify certificate ownership
Related CVEs
CVE-2024-58073
CVSS 5.5Authentication bypass vulnerability in Veeam Service Provider Console allowing unauthenticated attackers to impersonate managed agents and obtain their credentials via GUID-based identity spoofing.
Affected Products:
Veeam Service Provider Console (VSPC) – < 9.3.0.35057, 9.2.1.33875 and earlier
Exploit Status:
proof of conceptCVE-2024-58072
CVSS 7.8Arbitrary file write vulnerability in Veeam Service Provider Console allowing authenticated attackers to write files to arbitrary locations on the management server, leading to potential remote code execution.
Affected Products:
Veeam Service Provider Console (VSPC) – < 9.3.0.35057, 9.2.1.33875 and earlier
Exploit Status:
proof of conceptCVE-2024-58067
CVSS 5.5Memory exhaustion denial of service vulnerability in Veeam Service Provider Console allowing unauthenticated attackers to cause service disruption through unbounded packet buffering.
Affected Products:
Veeam Service Provider Console (VSPC) – < 9.3.0.35057, 9.2.1.33875 and earlier
Exploit Status:
no public exploitReferences:
CVE-2024-58071
CVSS 5.5Unauthenticated access vulnerability in Veeam Service Provider Console allowing attackers to access proxied appliance API with Portal Administrator privileges during session initiation windows.
Affected Products:
Veeam Service Provider Console (VSPC) – < 9.3.0.35057, 9.2.1.33875 and earlier
Exploit Status:
no public exploitReferences:
MITRE ATT&CK® Techniques
Exploitation of Remote Services
Exploit Public-Facing Application
Valid Accounts
Use Alternate Authentication Material: Application Access Token
Access Token Manipulation
Server Software Component: Web Shell
Archive Collected Data: Archive via Utility
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
NIST Cybersecurity Framework 2.0 – Access Control Policy and Procedures
Control ID: PR.AC-1
NYDFS 23 NYCRR 500 – Penetration Testing and Vulnerability Assessments
Control ID: 500.15(a)(3)
DORA – Identification of ICT Risk
Control ID: Article 8
CISA Zero Trust Maturity Model 2.0 – Multi-Factor Authentication Implementation
Control ID: Identity.IM.L2-01
NIS2 Directive – Cybersecurity Risk Management Measures
Control ID: Article 21(2)(a)
PCI DSS 4.0 – Software Security Testing
Control ID: 6.2.4
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Information Technology/IT
Critical infrastructure vulnerability in Veeam Service Provider Console creates unauthenticated RCE risk for IT service providers managing multi-tenant backup environments across customer networks.
Computer Software/Engineering
Software companies using Veeam backup solutions face lateral movement and privilege escalation risks through compromised agent certificates in multi-cloud hybrid environments.
Health Care / Life Sciences
Healthcare organizations risk HIPAA compliance violations through unencrypted traffic exposure and potential data exfiltration via compromised backup management consoles.
Financial Services
Financial institutions face zero trust network failures and east-west traffic security breaches through backup infrastructure compromise affecting PCI compliance requirements.
Sources
- A GUID is Not a Credential: Unauthenticated RCE in Veeam Service Provider Consolehttps://bishopfox.com/blog/a-guid-is-not-a-credential-unauthenticated-rce-in-veeam-service-provider-consoleVerified
- Veeam KB4893 - Security Vulnerabilities in Service Provider Consolehttps://www.veeam.com/kb4893Verified
- CVE-2024-58073 Detection Toolhttps://github.com/BishopFox/CVE-2024-58073-checkVerified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.
Aviatrix Zero Trust CNSF would likely limit the scope and blast radius of this multi-tenant backup infrastructure compromise by constraining lateral movement between customer environments and reducing attacker reachability through segmentation controls.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: Zero Trust network segmentation could have limited the attacker's ability to directly reach the vulnerable Veeam console management interface from untrusted network segments, reducing the attack surface exposure.
Control: Zero Trust Segmentation
Mitigation: Workload-level segmentation policies may have constrained the scope of certificate issuance by limiting which network segments and identities could access the certificate dispatcher service functionality.
Control: East-West Traffic Security
Mitigation: Microsegmentation policies could have significantly limited lateral movement by restricting which customer environments and backup systems the compromised agent credentials could access, reducing cross-tenant exposure.
Control: Multicloud Visibility & Control
Mitigation: Enhanced traffic visibility and behavioral analysis may have detected anomalous communication patterns within the agent protocol flows, potentially alerting on unusual command and control activities.
Control: Egress Security & Policy Enforcement
Mitigation: Controlled egress policies could have limited unauthorized data transfers by restricting which destinations and protocols compromised backup agents could use to exfiltrate sensitive customer information.
While web shell deployment may still occur, segmentation controls would likely limit the scope of compromise to specific network zones, reducing the attacker's ability to impact all customer environments simultaneously.
Impact at a Glance
Affected Business Functions
- Backup and Recovery Services
- Multi-tenant Data Management
- Managed Service Provider Operations
- Customer Data Protection
Estimated downtime: 7 days
Estimated loss: $500,000
Potential compromise of backup agent credentials providing unauthorized access to customer backup infrastructure and multi-tenant backup data across all managed organizations. Agent certificates provide authenticated positions in customer backup environments.
Recommended Actions
Key Takeaways & Next Steps
- • Deploy Zero Trust Segmentation to restrict agent communication ports (TCP/9999) to authorized subnets only, preventing unauthorized network access to backup infrastructure
- • Implement Multicloud Visibility & Control to detect anomalous agent authentication patterns and repeated certificate issuance requests indicating impersonation attempts
- • Enable Egress Security & Policy Enforcement to monitor and control outbound traffic from backup servers, detecting unauthorized data movement and command channels
- • Deploy Cloud Firewall (ACF) with URL filtering to prevent web shell deployment and block unauthorized internet-bound communications from management servers
- • Establish Threat Detection & Anomaly Response capabilities to baseline normal backup agent behavior and alert on certificate validation failures followed by channel replacements



