Threats / Veeam / CVE-2024-40711
CVE-2024-40711
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Veeam Backup & Replication vulnerability
Veeam Backup & Replication contains an unauthenticated deserialization vulnerability enabling remote code execution. The flaw is actively exploited in ransomware campaigns.
Verdict
Today item, not a backlog item.
An unauthenticated attacker can deserialize untrusted data in Veeam Backup & Replication to achieve remote code execution without credentials. Active exploitation in ransomware operations confirms real-world weaponization.
CISA KEV Yes · 2024-10-173Ransomware use Flagged3EPSS 0.88193 (verify live)4Exploit Weaponized · public PoC5
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
29 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-10-17), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.88193 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Veeam, Backup & Replication. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-502 Deserialization of Untrusted Data — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious serialized object and send it to the exposed Veeam service without authentication.
Business
Backup infrastructure becomes an entry point, bypassing perimeter defenses that assume backup systems are isolated.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I trigger deserialization of my payload, causing arbitrary code execution on the Veeam server with service privileges.
Business
Attacker gains initial foothold with elevated access to backup systems and stored credentials.
3
Lateral reach — past segmentation narrative 3
Attacker
I use the compromised backup server to access backup repositories and enumerate the network for high-value targets.
Business
Ransomware operators obtain visibility into protected assets and backup locations across the enterprise.
4
Data at risk — exfiltration narrative 4
Attacker
I deploy ransomware payloads from the backup infrastructure to encrypt production systems and backups simultaneously.
Business
Recovery options are eliminated; ransom demands become coercive with no restore path available.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05