CVE-2022-26501 [Exploited] | Veeam Backup \& Replication

CVE-2022-26501 is rated Critical Active Threat (100/100): CVSS Critical severity, with high exploitation likelihood (EPSS 75.40%, 99th percentile). CISA KEV confirms active exploitation (added 2022-12-13) affecting Veeam / Backup & Replication. a weakness (CWE-306) Unauthenticated remote administrative access may be possible. EPSS rose +8.67% over the last day, indicating growing attacker interest. The CISA remediation deadline has passed—treat as an emergency patch priority.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-05-06	66.73%	75.40%	+8.67%
2	2025-12-29	67.19%	66.73%	-0.46%
3	2025-12-18	—	67.19%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-05-06

66.73%

75.40%

+8.67%

2025-12-29

67.19%

66.73%

-0.46%

2025-12-18

—

67.19%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
9.8	3.1	CRITICAL	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	3.9	5.9	[email protected]
9.8	3.1	CRITICAL	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	3.9	5.9	134c704f-9b21-4f2e-91b3-4a467353bcc0
10.0	2.0	HIGH	`AV:N/AC:L/Au:N/C:C/I:C/A:C` Click to expand Access vector (AV:N) Can be exploited remotely over network reachability. Access complexity (AC:L) Exploitation conditions are straightforward and predictable. Authentication (AU:N) No authentication is required. Confidentiality impact (C:C) Complete confidentiality impact. Integrity impact (I:C) Complete integrity impact. Availability impact (A:C) Complete availability impact.	10.0	10.0	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

9.8

3.1

CRITICAL

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

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

3.9

5.9

[email protected]

9.8

3.1

CRITICAL

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

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

3.9

5.9

134c704f-9b21-4f2e-91b3-4a467353bcc0

10.0

2.0

HIGH

AV:N/AC:L/Au:N/C:C/I:C/A:C Click to expand

Access vector (AV:N): Can be exploited remotely over network reachability.
Access complexity (AC:L): Exploitation conditions are straightforward and predictable.
Authentication (AU:N): No authentication is required.
Confidentiality impact (C:C): Complete confidentiality impact.
Integrity impact (I:C): Complete integrity impact.
Availability impact (A:C): Complete availability impact.

10.0

[email protected]

Affected software / configurations for CVE-2022-26501

Vendor	Product	Version	Raw CPE
veeam	veeam_backup_\&_replication	>= 10.0.0.4442, < 10.0.1.4854	cpe:2.3:a:veeam:veeam_backup_\&_replication::::::::
veeam	veeam_backup_\&_replication	>= 11.0.0.825, < 11.0.1.1261	cpe:2.3:a:veeam:veeam_backup_\&_replication::::::::
veeam	veeam_backup_\&_replication	10.0.1.4854	cpe:2.3:a:veeam:veeam_backup_\&_replication:10.0.1.4854:-::::::
veeam	veeam_backup_\&_replication	10.0.1.4854	cpe:2.3:a:veeam:veeam_backup_\&_replication:10.0.1.4854:p20201202::::::
veeam	veeam_backup_\&_replication	10.0.1.4854	cpe:2.3:a:veeam:veeam_backup_\&_replication:10.0.1.4854:p20210609::::::
veeam	veeam_backup_\&_replication	11.0.1.1261	cpe:2.3:a:veeam:veeam_backup_\&_replication:11.0.1.1261:-::::::
veeam	veeam_backup_\&_replication	11.0.1.1261	cpe:2.3:a:veeam:veeam_backup_\&_replication:11.0.1.1261:p20211123::::::
veeam	veeam_backup_\&_replication	11.0.1.1261	cpe:2.3:a:veeam:veeam_backup_\&_replication:11.0.1.1261:p20211211::::::

References for CVE-2022-26501

URL	Tags
https://veeam.com	Vendor Advisory
https://www.veeam.com/kb4288	Vendor Advisory
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2022-26501	US Government Resource

URL

CVE-2022-26501

CISA KEV Record for CVE-2022-26501

Exploit prediction scoring system (EPSS) score for CVE-2022-26501

Common vulnerability scoring system (CVSS) metrics for CVE-2022-26501

Weakness enumeration for CVE-2022-26501

Affected software / configurations for CVE-2022-26501

References for CVE-2022-26501