CVE-2024-40711: Veeam Backup and Replication Deserialization Vulnerability

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-08 00:03 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

A deserialization of untrusted data vulnerability with a malicious payload can allow an unauthenticated remote code execution (RCE).

Description quoted from the CVE record (assigned by hackerone, published 2024-09-07).

Weakness: CWE-502 Deserialization of Untrusted Data

How it can be exploited

Exploitable over the network with low attack complexity needing no privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CISA assessment (SSVC): CISA assesses exploitation as active. Automatable: yes. Technical impact: total.

On CISA KEV since
2024-10-17
US federal deadline
2024-11-07
Ransomware use
Yes

Public exploit evidence (Exploit Observer)

Exploit Observer found 2 Nuclei templates, 7 code repositories and 4 research write-ups naming this CVE.

Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.

See all 19 references on Exploit Observer

Live scores

EPSS
0.904
very likely to be attacked soon
VEDAS
0.981
strong exploit evidence
On CISA KEV
Yes, since 2024-10-17
Detection rule
Nuclei · Suricata
EPSS (chance of attack)
10No cve-scores data 2026-02-22 to 2026-08-08no data0.1CVE-2024-40711 EPSS over time2025-042026-11-08
VEDAS (exploit evidence)
10No cve-scores data 2026-02-22 to 2026-08-08no data0.5CVE-2024-40711 VEDAS over time2025-042026-11-08

Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish.

Who is affected

ProductAffectedNot affected
Veeam Backup and Recoveryfrom 12.1.2 up to and including 12.1.2Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Vendor guidance:

How to detect it

Nuclei template (active check)

Veeam - Insecure Deserialization

A deserialization of untrusted data vulnerability with a malicious payload can allow an unauthenticated remote code execution (RCE).

Name and description quoted from the template, written by VEDAS.

The template sends 1 request (GET /api/v1/serverinfo); it decides using status, word matchers. Severity in the template: critical. Marked as not yet verified against a live vulnerable target.

Run it against a host you own or are authorised to test:

bash
nuclei -u https://your-host -t CVE-2024-40711.yaml
Show the template (44 lines)
yaml
id: CVE-2024-40711

info:
  name: "Veeam - Insecure Deserialization"
  author: vedas-arpsyndicate
  severity: critical
  description: |
    A deserialization of untrusted data vulnerability with a malicious payload can allow an unauthenticated remote
    code execution (RCE).
  reference:
    - https://www.exploit.observer/?keyword=CVE-2024-40711&match=exact
    - https://subdomain.center/?engine=ammonites&keyword=veeam&match=exact
  classification:
    cvss-metrics: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
    cvss-score: 9.8
    cve-id: CVE-2024-40711
    cwe-id: CWE-502
  metadata:
    verified: false
  tags: cve,cve2024,veeam,backup,unauth,passive,kev,vkev,vuln
http:
  - method: GET
    path:
      - "{{BaseURL}}/api/v1/serverinfo"
    headers:
      X-Api-Version: 1.1-rev1

    matchers-condition: and
    matchers:
      - type: word
        part: body
        words:
          - '"databaseVendor":'
          - '"databaseContentVersion":'
        condition: and

      - type: word
        part: content_type
        words:
          - "application/json"

      - type: status
        status:
          - 200

CVE-2024-40711.yaml on GitHub

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2024-40711 Veeam - Insecure Deserialization. Add them to your Suricata rule set and reload.

Show the rules
suricata
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2024-40711 Veeam - Insecure Deserialization"; flow:established,to_server; http.uri; content:"/api/v1/serverinfo"; nocase; fast_pattern; classtype:web-application-attack; reference:cve,CVE-2024-40711; reference:url,https://www.exploit.observer/?keyword=CVE-2024-40711&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=veeam&match=exact; sid:1009505; rev:1;)

CVE-2024-40711.rules on GitHub

Advisories on this CVE

References

Government sources

Other references

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, CISA KEV, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.

Supporting partners

Feasible SecurityAskealGoTrust