Skip to main content
Mallory
CriticalVulnerability

CVE-2024-29212: Remote Code Execution in Veeam Service Provider Console

Published May 13, 2024 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.9Critical · v3
EPSS1.6%76th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Veeam Software
IdentifiersCVE-2024-29212CWE-502 · Deserialization of Untrusted Data

CVE-2024-29212 is a critical unsafe deserialization vulnerability in Veeam Service Provider Console (VSPC). The flaw arises from an unsafe deserialization method used by the VSPC server during communication between the management agent and its components. Under certain conditions, a remote authenticated attacker with user-level privileges can supply crafted serialized data that is processed by the VSPC server, leading to remote code execution on the server machine. Affected releases include unsupported VSPC versions 4.0, 5.0, and 6.0, as well as 7.0 versions earlier than 7.0.0.18899 and 8.0 versions earlier than 8.0.0.19236.

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 allows execution of attacker-controlled code on the Veeam Service Provider Console server. This can result in full compromise of the VSPC host, including unauthorized access to application data and managed-environment information, alteration of console configuration, use of the server as a pivot point for further intrusion, and disruption of backup-management operations.

Mitigation

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

If immediate patching is not possible, reduce exposure of the VSPC server and tightly restrict access to the management interfaces and agent-to-server communication paths to only trusted administrative systems and networks. Minimize the number of accounts with access to VSPC, review and limit user-level permissions, monitor for anomalous activity involving management agents and console components, and prioritize emergency upgrade because no complete mitigation is described as equivalent to patching.

Remediation

Patch, then assume compromise.

Upgrade Veeam Service Provider Console to a fixed release. Supported remediation versions identified are 7.0.0.18899 and 8.0.0.19236 or later. Deployments running end-of-support versions 4.0, 5.0, or 6.0 should be migrated to a supported, patched release. Follow the vendor security guidance associated with the VSPC updates and ensure only supported versions remain in service.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Veeam SoftwareVeeam Service Provider Consoleapplication
FAQ

Frequently asked questions

Is CVE-2024-29212 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2024-29212 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2024-29212?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2024-29212.
Is there a patch for CVE-2024-29212?
Upgrade Veeam Service Provider Console to a fixed release. Supported remediation versions identified are 7.0.0.18899 and 8.0.0.19236 or later.
What products are affected by CVE-2024-29212?
Veeam Software Veeam Service Provider Console.
How severe is CVE-2024-29212?
CVE-2024-29212 has a CVSS v3 score of 9.9 (Critical) and an EPSS score of 1.6% (76th percentile) as of Oct 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 activityCommunity discussion across Reddit, Mastodon, and other social sources.