Skip to content
Server Security Center
KEVcritical9.8 Used in ransomware campaigns

CVE-2022-26501: Veeam Backup & Replication Remote Code Execution

Veeam Backup & Replication · listed in the CISA catalog of actively exploited vulnerabilities since 2022-12-13.

CVSS v3.1 (CISA ADP)
9.8
critical
EPSS (exploit probability, 30 days)
4.1%
higher than 91% of all CVEs
Added to CISA KEV
2022-12-13
US federal due date 2023-01-03
Automatable (CISA SSVC)
yes
technical impact: total

CVE-2022-26501 explained

CVE-2022-26501 is an incorrect access control flaw in Veeam Backup & Replication 10.x and 11.x, classified as missing authentication for a critical function. It can lead to remote code execution on backup servers. CISA lists it as known exploited, including in ransomware campaigns, so it is a high priority for patching.

Impact

An unauthenticated attacker with network access can exploit the flaw with low complexity and no user interaction. Successful exploitation gives high impact to confidentiality, integrity and availability. CISA rates it automatable, so attackers can exploit it at scale, with total technical impact: full control of the affected component. Attackers are known to exploit it, and it is known to be used in ransomware campaigns.

Who is affected

The description names Veeam Backup & Replication 10.x and 11.x as affected. The CVE record itself lists no structured affected versions. The CVE record names no fixed version. This does not mean no fix exists. CISA's required action is to apply updates per vendor instructions, so check the Veeam vendor advisory for the updates that address this issue.

Written with AI from the data on this page and checked against it automatically.

Official description

Veeam Backup & Replication 10.x and 11.x has Incorrect Access Control (issue 1 of 2).

CISA required action: Apply updates per vendor instructions.

CISA notes

How to fix it

  • The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
  • Vendor advisory: veeam.com
  • CISA's deadline for US federal agencies: 2023-01-03 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Identify all Veeam Backup & Replication servers running 10.x or 11.x.
  2. Apply the updates described in the Veeam vendor advisory, as CISA's required action states.
  3. Block internet access to Veeam Backup & Replication servers and limit network access to trusted administrative hosts.
  4. Check backup servers for signs of compromise, given confirmed exploitation and ransomware use.
  5. Verify that backups remain intact and recoverable after patching.

The CVE record names no fixed version. Follow the Veeam vendor advisory and CISA's required action to apply updates per vendor instructions. Until updates are applied, restrict network access to Backup & Replication servers to trusted hosts only and monitor them for signs of compromise.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-306 Missing Authentication for Critical Function

Questions about CVE-2022-26501

Is CVE-2022-26501 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-12-13 and notes known use in ransomware campaigns. US federal agencies had a due date of 2023-01-03.
Does an attacker need credentials?
No. The flaw is a missing authentication issue. It can be exploited over the network without privileges or user interaction.
Which version fixes the issue?
The CVE record names no fixed version. Consult the Veeam vendor advisory for the updates to apply, as CISA's required action instructs.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.