HIGH · CVSS 8.8 CISA Known Exploited Vulnerability

CVE-2022-26500

Veeam Backup & Replication Remote Code Execution Vulnerability

Veeam Backup & Replication

Improper limitation of path names in Veeam Backup & Replication 9.5U3, 9.5U4,10.x, and 11.x allows remote authenticated users access to internal API functions that allows attackers to upload and execute arbitrary code.

CVSS
8.8
HIGH
EPSS
5.8%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
17 Mar 2022
CWE-22

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 13 December 2022. US federal agencies were required to remediate it by 3 January 2023. CISA records this vulnerability as known to be used in ransomware campaigns.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 5.8%, which is higher than 93% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Frequently asked questions

Is CVE-2022-26500 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2022-26500.

What does CVE-2022-26500 affect?

CVE-2022-26500 affects Veeam Backup & Replication. Improper limitation of path names in Veeam Backup & Replication 9.5U3, 9.5U4,10.x, and 11.x allows remote authenticated users access to internal API functions that allows attackers to upload and execute arbitrary code.

How severe is CVE-2022-26500?

CVE-2022-26500 is rated HIGH with a CVSS base score of 8.8. EPSS puts the probability of exploitation in the next 30 days at 5.8%, higher than 93% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 3 January 2023.

How should organisations respond to CVE-2022-26500?

Apply the vendor patch for Veeam Backup & Replication as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.