CVE-2024-40711
A deserialization of untrusted data vulnerability with a malicious payload can allow an unauthenticated remote code execution (RCE).
do firstApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? Partly. Insecure deserialization payloads can be built from many different gadget chains, so WAF signatures only catch the known ones.
Also consider: allow-list classes · patch
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2024-40711 being exploited?
Yes. CVE-2024-40711 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2024-40711?
CVE-2024-40711 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2024-40711?
Yes. A fix has been recorded for CVE-2024-40711. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2024-40711 affect?
CVE-2024-40711 affects veeam:veeam_backup_\&_replication. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected<= 12.1.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
public exploits
Unvetted proof-of-concept code on GitHub: 2 GitHub proofs of concept · 1 Nuclei template
- Veeam Backup & Replication - Unauthenticated · detection template · critical
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- yes
- technical impact
- total
Assessed by CISA 29 Oct 2024 (SSVC 2.0.3).
timeline
- 7 Sept 2024Published
- 15 Sept 2024First proof-of-concept repository on GitHub (unvetted) · 7 days later
- 17 Oct 2024Added to CISA KEV (exploited in the wild) · 32 days later
- 29 Oct 2024CISA SSVC assessment: exploitation active · 13 days later
- 7 Nov 2024CISA remediation due date (US federal agencies) · 8 days later
- 21 Oct 2025CVE record last updated · 349 days (about 12 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 377 days (about 1 year) later
- Linkveeam.com /kb4649
- Linklabs.watchtowr.com /veeam-backup-response-rce-with-auth-but-mostly-without-auth-cve-2024-40711-2/
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-40711
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Nuclei templates: detection templates
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.